Å·±¦ÓéÀÖ

This book is gold. I wish I had read it when I was struggling to break down a legacy monolith into microservices. A lot of the problems I faced were actually covered in this book, and even if I couldn't have avoided them, I would have been better prepared for them. The book isn't just about microservices, but it also covers how to break down your codebase and persistence layer to make them more modular. It even helps you to consider whether you need to do this in the first place and the cost of doing it.

I think it would be great if this book had a second edition with more practical examples. For instance, most people are aware that to decouple and migrate part of your database to a new microservice, you need to copy the data and start using it. However, it's actually more challenging to do than we realize, especially if you want to achieve zero downtime. Simple backup and restore, along with some synchronization strategy, may not be enough. It can be a real challenge to avoid a maintenance window while ensuring that the data is consistent between both databases (consider using write-ahead log for synchronization and MD5 checksum hash function for testing).

I'm currently reading Software Architecture: The Hard Parts, and I think these two books complement each other pretty well.