The State of Microservices: Is the Monolith Returning?
Why we recommend a modular monolith to most teams, and the signals that tell you when to split.
Microservices solved an organizational problem for very large companies and created operational problems for everyone else. The pendulum is swinging back.
A modular monolith with clear domain boundaries gives you most of the benefits: independent modules, clear ownership, simple deployments. You extract a service when one module needs a different scaling profile or a different team cadence.
The signal to split is rarely performance. It is usually coordination cost between teams.
Working on something similar?
Talk to a senior engineer about it. No salespeople.