ArchitectureMicroservicesBackend

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.

Robel Fekadu, Backend Engineer 18 February 2026 7 min read

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.

Book a call

Start a conversation

Let’s solve a real problem together.

Whether you need software built, a network installed or a partner for a digital transformation program, your first conversation is with the people who will do the work.

We reply within one business day. Based in Addis Ababa, working with partners in Ethiopia and beyond.

2026
Founded in Addis Ababa, Ethiopia
2
Focus areas: software, networking & IT
4
Core values: Service, Wisdom, Stewardship, Excellence
3
Founding leadership team