Monolith to Microservices (From monolith to microservice n)

This book, Monolith to Microservices, was written by Sam Newman, who contributed to the rise of microservices with his book Building Microservices. This book is definitely good, but it’s not a continuation of the microservices book, but rather a prequel to the original book. This is stated by the author in the introduction, sprinkling his head with ashes regarding the fact that he opened a Pandora’s box with microservices, which led to the mass adoption of them all in a row without a deep understanding of the limits of applicability of this approach:) In the new book, the author discusses such topics as: What is a microservice and what size it can be - by bounded context

• what logic to use to decompose your monolith on microservices - suddenly there is another three-letter acronym DDD Whether you always need microservices is logical:) How to avoid migration from monolith to microservices How to cut monolithic code How to deal with data sources - ala pilim database What pains will you have when instead of one monolith you have a collection of microservices, in which the complexity of operation increases by orders of magnitude, if you use the same approaches as for the operation of the monolith

I like the author's closing words on two ideas he wanted to share in his book: "First, give yourself enough space and gather the right information to make rational decisions. Don’t just copy others; think instead about your problem and your context, assess the options, and move forward, while being open to change if you need to later. Second, remember that incremental adoption of microservices, and many of the associated technologies and practices, is key" Very logical and understandable thoughts that make you soberly look at any approaches to solving problems. And yes, microservices too:)

#SystemDesign #DistributedSystems #SoftwareArchitecture #Architecture #Software #SoftwareDevelopment