The rationale behind microservices
There isn’t a clear definition for microservices architecture, except in a famous blog by Martin Fowler and James Lewis entitled Microservices (https://www.martinfowler.com/articles/microservices.html), published in March 2014, which explains the characteristics of microservices architecture. Scrolling through the characteristics in the article, you can find many of them really align with bounded context principles. If you are asking yourself why you should move your project to a microservices architecture style, you need to analyze these characteristics and check how they relate to DDD. Four of them must capture your attention:
- Organized around business capabilities: Usually, when breaking down a large application into smaller parts, management often organizes teams based on technological layers. This is a direct consequence of Conway’s Law (Melvin Conway, 1968, https://martinfowler.com/bliki/ConwaysLaw.html). This approach...
