Rethinking Microservice Decomposition: A Team-Driven Approach

Integrating project management and technical trade-offs for agile system evolution

My girl

Not a member? You can still check out this article through here.

Recently, I have had some insights about microservice decomposition.

In the past, when discussing microservices decomposition, we usually start from the technical perspective, identify the domain boundary and then cut into the problem from the technical perspective to find out the appropriate decomposition solution.

The book Monolith to Microservices describes a number of technical "patterns" that cover most of the scenarios at a high level.

Monolith to Microservices

In general, there are three approaches:

1. Split the database first, then the code
2. Split the code first, then the database
3. Split them both at once

However, the third approach is highly discouraged in the book, and in my personal experience as well.