Long path to better systems that last longer and make engineers and customers happier KEY FEATURES ● Guidance, trade-offs analysis, principles, and insights on understanding complex microservices and monoliths problems and solutions at scale. ● In-depth coverage of anti-patterns, allowing the reader to avoid pitfalls and understand how to handle architecture at scale better. ● Concepts and lessons learned through experience in performing code and data migration at scale with complex architectures. Best usage of new technology using the right architecture principles. DESCRIPTION This book is a comprehensive guide to designing scalable and maintainable software written by an expert. It covers the principles, patterns, anti-patterns, trade-offs, and concepts that software developers and architects need to understand to design software that is both scalable and maintainable. The book begins by introducing the concept of monoliths and discussing the challenges associated with scaling and maintaining them. It then covers several anti-patterns that can lead to these challenges, such as lack of isolation and internal shared libraries. The next section of the book focuses on the principles of good software design, such as loose coupling and encapsulation. It also covers several software architecture patterns that can be used to design scalable and maintainable monoliths, such as the layered architecture pattern and the microservices pattern. The final section of the book guides how to migrate monoliths to distributed systems. It also covers how to test and deploy distributed systems effectively. WHAT YOU WILL LEARN ● Understand the challenges of monoliths and the common anti-patterns that lead to them. ● Learn the principles of good software design, such as loose coupling and encapsulation. ● Discover software architecture patterns that can be used to design scalable and maintainable monoliths. ● Get guidance on how to migrate monoliths to distributed systems. ● Learn how to test and deploy distributed systems effectively. WHO THIS BOOK IS FOR This book is for software developers, architects, system architects, DevOps engineers, site reliability engineers, and anyone who wants to learn about the principles and practices of modernizing software architectures. The book is especially relevant for those who are working with legacy systems or want to design new systems that are scalable, resilient, and maintainable. TABLE OF CONTENTS 1. What’s Wrong with Monoliths? 2. Anti-Patterns: Lack of Isolation 3. Anti-Patterns: Distributed Monoliths 4. Anti-Patterns: Internal Shared Libraries 5. Assessments 6. Principles of Proper Services 7. Proper Service Testing 8. Embracing New Technology 9. Code Migrations 10. Data Migrations 11. Epilogue

Salary surveys worldwide regularly place software architect in the top 10 best jobs, yet no real guide exists to help developers become architects. Until now. This book provides the first comprehensive overview of software architecture’s many aspects. Aspiring and existing architects alike will examine architectural characteristics, architectural patterns, component determination, diagramming and presenting architecture, evolutionary architecture, and many other topics. Mark Richards and Neal Ford—hands-on practitioners who have taught software architecture classes professionally for years—focus on architecture principles that apply across all technology stacks. You’ll explore software architecture in a modern light, taking into account all the innovations of the past decade. This book examines: Architecture patterns: The technical basis for many architectural decisions Components: Identification, coupling, cohesion, partitioning, and granularity Soft skills: Effective team management, meetings, negotiation, presentations, and more Modernity: Engineering practices and operational approaches that have changed radically in the past few years Architecture as an engineering discipline: Repeatable results, metrics, and concrete valuations that add rigor to software architecture

The software development ecosystem is constantly changing, providing a constant stream of new tools, frameworks, techniques, and paradigms. Over the past few years, incremental developments in core engineering practices for software development have created the foundations for rethinking how architecture changes over time, along with ways to protect important architectural characteristics as it evolves. This practical guide ties those parts together with a new way to think about architecture and time.

There are no easy decisions in software architecture. Instead, there are many hard parts--difficult problems or issues with no best practices--that force you to choose among various compromises. With this book, you'll learn how to think critically about the trade-offs involved with distributed architectures. Architecture veterans and practicing consultants Neal Ford, Mark Richards, Pramod Sadalage, and Zhamak Dehghani discuss strategies for choosing an appropriate architecture. By interweaving a story about a fictional group of technology professionals--the Sysops Squad--they examine everything from how to determine service granularity, manage workflows and orchestration, manage and decouple contracts, and manage distributed transactions to how to optimize operational characteristics, such as scalability, elasticity, and performance. By focusing on commonly asked questions, this book provides techniques to help you discover and weigh the trade-offs as you confront the issues you face as an architect. Analyze trade-offs and effectively document your decisions Make better decisions regarding service granularity Understand the complexities of breaking apart monolithic applications Manage and decouple contracts between services Handle data in a highly distributed architecture Learn patterns to manage workflow and transactions when breaking apart applications

Proven techniques and principles for modernizing legacy systems into new architectures that deliver serious competitive advantage. For a business to thrive, it needs a modern software architecture that is aligned with its corporate architecture. This book presents concrete practices that sync software, product, strategy, team dynamics, and work practices. You’ll evolve your technical and social architecture together, reducing needless dependencies and achieving faster flow of innovation across your organization. In Architecture Modernization: Socio-technical alignment of software, strategy, and structure you’ll learn how to: Identify strategic ambitions and challenges using listening and mapping tours Visualize your business landscape and crucial capabilities with Wardley Mapping Create a product taxonomy as a framework for your architecture Run big picture EventStorming workshops to map business domains Apply Team Topologies patterns to identify and refine value streams Design loosely coupled, domain-aligned software architectures Build internal developer platforms for rapid, reliable evolution Implement data mesh principles and tools to revolutionize data engineering Deliver compelling modernization roadmaps focused on continuous value Architecture Modernization: Socio-technical alignment of software, strategy, and structure shows you how to turn the practice of architecting systems into a transformative process for your entire company. Chapter-by-chapter, you’ll identify the reasons and benefits of modernization, design an architecture that works for your business, and then implement your new approach in a progressive and sustainable manner. Every technique is illustrated with insightful industry examples and an interactive Miro board that lets you dig deeper. Forewords by Matthew Skelton and Xin Yao. Purchase of the print book includes a free eBook in PDF, Kindle, and ePub formats from Manning Publications. About the technology The decisions you make about your software are inherently connected to the decisions you make about your business. Why not turn the mundane task of modernizing legacy systems into a transformative process for your entire company? This book shows you how! It reveals a socio-technical approach to align your software and products with organizational dynamics and ways of working. About the book Architecture Modernization: Socio-technical alignment of software, strategy, and structure presents a clear path for upgrading your entire organization when you re-imagine your software. In it, you’ll learn to combine practices like Domain-Driven Design, Event Storming, and Wardley Mapping to discover user needs, design optimal architecture, and avoid falling back into old habits. Provocative examples from Danske, Salesforce, the UK Government, and others show the real-world result of each approach, identifying techniques you can apply effectively in your own business. What's inside Uncover cross-org challenges and opportunities A product-centric approach to architecture Envision architecture as a portfolio to prioritize investment About the reader For CTOs, tech leads, and principal engineers who decide on architecture and organization design. About the author Nick Tune helps organizations modernize their architectures through empowered product teams and continuous delivery. Jean-Georges Perrin builds innovative and modern data platforms. The technical editor on this book was Kamil Nicieja. Table of Contents 1 What is architecture modernization? 2 Preparing for the journey 3 Business objectives 4 Listening and mapping tours 5 Wardley Mapping 6 Product taxonomy 7 Big picture EventStorming 8 Product and domain modernization 9 Identifying domains and subdomains 10 Strategic IT portfolio 11 Team Topologies 12 Loosely coupled software architecture 13 Internal developer platforms 14 Data mesh revolutionizing data engineering 15 Architecture modernization enabling teams 16 Strategy and roadmaps 17 Learning and upskilling

Description
As an engineer, it can feel like there is never enough time for testing, designing, or delivering quality solutions. Managers often feel overwhelmed by the need to deliver new features to support their teams while managing vulnerabilities and security standards. Engineers often have to work with legacy systems and learn many new technologies simultaneously to be effective in their jobs. This book teaches you continuous modernization, a key skill for tackling modern and legacy software. By adopting the right mindset and techniques, you will improve systems and workflows, making everything more efficient over time.

Continuous modernization is your essential guide to updating old software systems into modern, efficient, and scalable applications. This book covers everything from changing your mindset and technical practices to business strategies and fostering a culture of innovation. It includes tips on unlearning outdated methods, embracing feedback, making smart decisions, ensuring stability, and applying modern design principles. With practical techniques and real-world examples, it provides the tools you need to modernize your software systems and achieve lasting success successfully.

By the end of this book, readers will master continuous modernization principles and practices. They will learn to spot areas needing improvement, create effective modernization strategies, and implement changes that boost value and efficiency. Additionally, they will understand how to build a culture of innovation and ongoing learning to keep their software systems up-to-date and competitive in a fast-changing tech world.

Key Features
● Develop the mindset to drive software success, delivering impactful changes with fewer resources.
● Explore patterns and anti-patterns in technical architecture, team dynamics, troubleshooting, and design.
● Gain insights on solving large-scale software modernization challenges, from culture to architecture.

What you will learn
● Learn patterns, anti-patterns, and tools to improve software architecture decisions.
● Eliminate limiting practices to improve development efficiency.
● Apply disciplined feedback loops to refine architecture and design decisions.
● Implement advanced troubleshooting techniques to prevent design flaws.
● Continuously refactor systems and scale modernization efforts in distributed architectures.

Who this book is for
Our book is for professionals in the field of computer science. It is for software architects, engineers, testers, managers, directors, and VPs. This is for individuals and teams who may or may not have a modernization project but care about improving individuals and systems daily.

Table of Contents
1. What is Continuous Modernization?
2. Unlearning
3. Discipline & Feedback
4. Decisions & Tradeoffs
5. Stability & Troubleshooting
6. Opportunistic Design
7. Continuous Refactoring
8. The Art of Selling
9. Effective Negotiation
10. Culture Shift
11. Epilogue

As the digital economy changes the rules of the game for enterprises, the role of software and IT architects is also transforming. Rather than focus on technical decisions alone, architects and senior technologists need to combine organizational and technical knowledge to effect change in their company’s structure and processes. To accomplish that, they need to connect the IT engine room to the penthouse, where the business strategy is defined. In this guide, author Gregor Hohpe shares real-world advice and hard-learned lessons from actual IT transformations. His anecdotes help architects, senior developers, and other IT professionals prepare for a more complex but rewarding role in the enterprise. This book is ideal for: Software architects and senior developers looking to shape the company’s technology direction or assist in an organizational transformation Enterprise architects and senior technologists searching for practical advice on how to navigate technical and organizational topics CTOs and senior technical architects who are devising an IT strategy that impacts the way the organization works IT managers who want to learn what’s worked and what hasn’t in large-scale transformation