Finished reading Monolith to Microservices by @samnewman
It is the top book for monolith decomposition practices⭐️⭐️⭐️
A few comments below 👇
It is the top book for monolith decomposition practices⭐️⭐️⭐️
A few comments below 👇
There is no technology clutter in this book, but practices, patterns, and insights you will need day to day while migrating from a monolith.
I think in diagrams, and having a diagram accompanying every pattern, every scenario helped me a lot with the understanding of the problem.
One of the most important advice in the book:
I’ve seen many customers choosing the aggregate as the microservices boundary rather than the bounded context. This leads to an explosion of too many services
I’ve seen many customers choosing the aggregate as the microservices boundary rather than the bounded context. This leads to an explosion of too many services
Another one is “Reversible and Irreversible decisions”. Many organizations spent many long hours of meetings on discussion reversible decisions, whereas high (negative) impact decisions are taken lightly (usually during urgency or due to lack of experience).
There is always some need for Enterprise Integration Patterns and Apache Camel @ApacheCamel 🐪😃
Change Data Capture pattern, really should be listed under database decompositions, as a data synchronization pattern
The comparison of different change data capture approaches (batch delta copier with transaction log poller) would benefit from some additional comparison such as this
Database-as-a-Service Interface Pattern: does not describe data virtualization like technologies (such as @teiid) which can offer a database like interfaces too
There is an honorary mention of @debezium as a good option for database mapping engine for database replication 👏
I love the practical tone of the book, the size and the level at which it is written: just enough context and technology details to explain the problem and explore the solutions
Reading it will show you that breaking a monolith is a complex trade-off journey. There are no best or bad practices but tradeoffs only. For every pattern and technique, there is an alternative, and also cases for not using it.
For those who can afford it, check out the printed copy, but if you cannot check the link for a sponsored copy here
END
END
Loading suggestions...