Modular Monolith vs Microservices: How to Choose
Modular monolith vs microservices: start with a modular monolith and extract services only when a real force demands it. The decision framework and the signals.
Topic hub
Service boundaries, gRPC, event-driven architecture, Kafka, and the organizational physics of polyglot platforms.
7 articles
Modular monolith vs microservices: start with a modular monolith and extract services only when a real force demands it. The decision framework and the signals.
Shared libraries in microservices promise reuse but quietly recouple services through a versioned dependency. When they help, when they hurt, and the rules.
Service dependency cycles make microservices impossible to deploy, test, or reason about in isolation. How to detect them and four ways to break them.
Bounded contexts are how you find real microservice boundaries: split where the same word means different things. The practical guide, not the DDD theory.
Service ownership boundaries decide whether microservices scale your org or stall it. Draw them by data ownership and team, not by code size. The rules.
Polyglot microservices break at the seams, not inside services. The 5 cross-language failure modes (deadlines, cancellation, errors, types, connections) and fixes.
FastAPI microservices done right: where they belong in a polyglot fleet, the async model that decides performance, and the worker math most teams skip.