Strategic Monoliths and Microservices: Driving Innovation Using Purposeful Architecture (Addison-Wesley Signature Series (Vernon))

Just finished reading the book "Strategic Monoliths and Microservices: Driving Innovation Using Purposeful Architecture" by Vaughn Vernon and Tomasz Jaskula.Unlike other software architecture books, this is a more conceptual book which focuses on strategic and high level concepts, especially those regarded monolithic and microservice architectures.The book did not advocate for Monoliths over Microservices, it focus on the best possible decision for the business circumstances and show the advantages of adopting a monolithic architecture on early lifecyle phases.Some highlights that should be shared:- Monoliths are not bad, Big Ball of Mud are bad and you can have it on Microservices architecture too.- Big Ball of Mud are situations where information are shared promiscuously among distant elements of the system, often to the point where nearly all the important information becomes global or duplicated. The overall structure of the system may never have been well defined.- Over the past several years, the words Monolith and Monolithic as applied to software have come to have very negative connotations. Even so, just because the vast majority of Monolithic legacy systems have arrived at the Big Ball of Mud zone, that doesn't mean it is a necessary destination. It's not the Monolith that's the problem - it's the mud.- Even if the ultimate system architecture is to be Microservices, there are advantages to the system to start out life as a Monolith. Not having a network between subsystems can prevent a lot of problems that are unnecessary to contend with early on and are quite counterproductive. When performance and scale indicators are trending toward the need to address theses issues, extracting one or more modules from a Monolith into Microservices is likely a reasonable way foward.- Even if the teams are convinced that a Microservices architecture is necessary, delaying the introduction of services separated by the computing network (See the fallacies of distributed computing) can help the team focus on actual business drivers rather than trying to cope with the distributed comuting overhead too early.- Choosing Microservices first is dangerous. Choosing Monoliths for the longterm is also dangerous.- Early on, it is best to choose a deployment option that supports fast experimentation, implementation, and delivery. This specifically points to using a Monolithic architecture in the early stages, because trying to solve distributed computing problems before the business problems are understood is an act of futility. Finding ways to to reduce the total distribution os computing resources or reducing the complexities as much as possible should be the top priority.- Microservices are not about the size but rather about the purpose. A single Bounded Context on its own would be very unlikely to be a Monolith, thinking of a Bounded Context as a Microservice isa a good enough place to start.- Not every system requires a Microservice architecture. Monoliths can be a viable alternative and architecture choice for many teams and enterprise situations.- There is no clear winner between modularized Monoliths and Microservices. As always, it is important to understand the circumstantial trade-offs.

This is an excellent book with a mix of theory, practical examples, and shared wisdom from years of experience. Very well written. Concise. Covering a broad spectrum of topics relevant to evaluating monoliths vs. micro services. I learned a great deal and now better understand the context of many other materials I’m consuming elsewhere.

Es difícil de leer por el tamaño de la letra que utilizaron

Just finished reading the book "Strategic Monoliths and Microservices: Driving Innovation Using Purposeful Architecture" by Vaughn Vernon and Tomasz Jaskula. It fills a much needed gap in the conversation around software architecture today.Unlike other software architecture books, which are more technical in nature, this book really gets into the why and how your organization can strategically innovate to establish a digital transformation.The book is meant for C-level and other business executives, as well as every role and level involved in leading software development, including software architects and dev team leads.It doesn’t go in-depth into technical implementation. That is saved for the next book, "Implementing Strategic Monoliths and Microservices"It outlines how to identify and set organizational goals, how to use strategic learning tools, how to drive business innovation, and whether a well-implemented monolith is more or less appropriate than a microservices architecture. It covers event storming, DDD, large-scale refactoring, and event-driven architectures.It’s a book centered on software architecture being an integral part of business strategy.The authors make it very real and practical by using a fictional insurance company, NuCoverage, and a digital transformation business scenario throughout the book, providing real world examples of how to apply the techniques and ideas presented.A few quotes from the book:“Steve Job’s advice: “You can’t look at the competition and say you’re going to do it better. You have to look at the competition and say you are going to do it differently.”“Imitation is not a strategy. Differentiation is.”“One of the biggest problems in software development is developing functionality and features within software that have little to no value to the business.”I highly recommend this book as well as the other books in the Vaugh Vernon Signature Series. Top quality authors and content.

Good book explaining how to build the rationale behind some decisions and give important tips about the right time. I've been reading but I haven't done yet.

A book so needed by the software industry and focusing on what's more needed, a book with a software perspective that addresses the business.Vaughn and Tomazs made a book accessible a complex topic as is strategic thinking towards Software Development. A book that helps not only Software Developers but people in other fields to __make the right questions to address the high-value business initiatives__.I do recommend this book to any software developer, architect, tech lead, or principal that works on complex domains. It gives you the right perspective and the tools to address these problems from a Strategic point of view.It's important that it gives _how_ and _why_ you should make decisions based on business. That's what makes more valuable the decisions made by engineering leadership. This book doesn't include the implementation part, which will come later in the next book, yet understanding this part is crucial to later have high-impact implementations. Without this good reasoning, it doesn't matter how good is the implementation if you are implementing the wrong thing.I hope you enjoyed it as much as I did! Already applying concepts in my day-to-day