Monolith to Microservices

It is an amazing book. It covers everything from start to end. If you want to travel the road of Microservices. It’s structured in a way that fits the mental model of monolith developers but to evaluate Microservices architecture. It’s going to serve a glossary of what to do & what not to do when doing Microservices. Starts with simple 3 questions, during the journey you would feel yeah it feels very real. But without single line of code. You will get answers along the way, from people problems, team ownership, tackling database, importance of DDD and suggestions on tool one has to learn along the way. Thanks Sam Newman for writing such an amazing book.

I like the book because it's short, easy to follow, and informationally dense. However, the patterns chapters really don't work well in the audiobook format because they are more of a reference so I'd rather have a hard copy when accessing those as needed.

Helpful ideas and patterns. Would have liked more prescriptive advice about the patterns and how to apply them.

As someone that has experienced the difficulties of this architectural style at scale, I can sincerely recommend the reading of this book. It's a fantastic set of patterns and practical advice. I like the tactical approach of the book while emphasis the strategical aspect first and foremost. I really enjoyed!

I loved Sam's other book on microservices, but this one addresses the key issue - you almost never build microservices from scratch. The last three companies I have worked at have all had monoliths they were trying to move off of, and even after deciding a microservice architecture was the right choice, the big problem was how to get off of the old one. And the biggest challenge, by far, is the data. This is where Mr. Newman's book shines - he has so many different smart and useful patterns for addressing data migration. I am putting them to use already. Highly recommended if you find yourself staring at this big ball of mud and feeling completely overwhelmed. This book will give you courage and prevent you from crawling into a corner and pulling a blanket over your head.

If I could give this book 10 stars, I would. This book not only strikes a profound balance between being succinct and going to great depths, it also addresses and considers competing approaches. Be ready to learn and elevate your game.

I enjoyed this book a lot more than Mr. Newman's previous Microservices book though it's still pretty high level. I think he comes across as a very competent and professional Independent Consultant. He doesn't try and sell anything, he asks the questions most consultants/vendors won't ask (i.e. Do you need Mircoservices? Do you need to breakup your Monolith? etc) He knows what he's talking about and he's confident enough to not feel like he has to sell you anything and he can speak frankly. Very impressive. My main complaint is the one I had for his other book which is there still is no detailed analysis of a Microservice. You still have no idea what one is just from reading this. Adnittedly though this isn't meant to be a Microservices book as much as a Monolith to Microservice book. But, having said that, it would have been fantastic to use a real or contrived Monolith example and break it down (in detail) to microservices. I'm sure that would doubled the book size, but it would been real concrete information.

Very good patterns and reasoning of when to use them. Also a good starting chapters discussing if and when microservices is the right solution.

muy buena informacion para seguir desarrollando arquitecturas

Clear, practical, and concise with many incredibly useful citations.

This book teach us many strategies to make a successful migration to microservices. I recommend it for those that will work with this.

I previously read Building Microservices by Sam Newman which was a great staying off point for Microservices. This book expands on that by including strategies to migrate from a monolith to microservices. The strategies are well explained and practical examples given to solidify the learning. Sam's way of teaching keeps things interesting while reinforcing the information. I can't recommend this enough for anyone planning to migrate from a monolith to microservices.

The book contains more than 250 pages and not just 150.