Tuesday, November 17, 2026 · Week 47 DE · EN · FR · ES Dark
Reboot Germany

Microservices or Monolith: When to Rebuild

Independent deployments can justify microservices. Business boundaries and operational demands determine whether a rebuild is worthwhile.

By Benedikt Langer March 31, 2026 4 min read
Microservices or Monolith: When to Rebuild

Microservices can enable teams to deploy independently and scale individual functions separately. They also create additional work in communication, data consistency and operations. A modular monolith combines distinct business modules in a single application and can be a useful starting point. Whether a rebuild is worthwhile depends on the specific bottleneck and the team’s capabilities.

Key takeaways

  • Independent deployments are a central reason for choosing microservices. The benefit arises when business domains can actually be changed and operated separately.
  • Distributed systems place greater demands on operations. Network failures, data consistency and request tracing must be considered in the design.
  • A modular monolith creates business boundaries within a single application. Whether a module can later be extracted depends, among other things, on its data and dependencies.

The benefits of independent services

In a microservices architecture, an application is divided into services with distinct business responsibilities. In principle, these can be developed, deployed and scaled independently of one another. This can help when individual domains have different change cycles or load profiles.

Dividing an application alone does not guarantee this independence, however. If several services must be changed and rolled out together for a single change, coordination between them remains necessary. Microsoft therefore recommends grouping functions that need to change together and aligning service boundaries with business domains.

The cost of distributed communication

A call between services travels over a network and can be delayed or fail. Long chains of such calls make troubleshooting harder and can increase response times. Operations therefore require, among other things, informative logs, monitoring and a way to trace related calls across service boundaries.

Data also becomes more demanding: when services are responsible for their own data, changes must be coordinated between them. A business transaction spanning several services cannot readily be treated like a single local database transaction. The consistency a business process requires should therefore be considered before defining service boundaries.

Shared database infrastructure is not necessarily the problem. According to Microsoft’s architectural guidance on data, what matters is whether services directly modify the same tables or schemas and thereby become dependent on one another.

Maintaining module boundaries in a monolith

A modular monolith divides a jointly deployed application into business modules with defined interfaces. This allows teams to make dependencies within the application visible and limit them. Joint deployment remains a deliberate feature: a change is rolled out with the application.

Module boundaries must be maintained and checked in the code. For Spring applications, Spring Modulith can check for cyclic module dependencies and access to internal packages, for example. The tool helps verify the structure, though it cannot replace a business decision about how to define the boundaries.

If a module is to run as a separate service later, its data, interfaces and dependencies must be considered alongside the code. A clean module structure can make this analysis easier. It does not automatically make extraction simple.

Aligning the rebuild with the bottleneck

Before making an architectural decision, teams should identify exactly what is slowing them down today. Are releases from different domains blocking one another? Does a function need to be scaled independently of the rest? Or do the difficulties lie mainly in unclear responsibilities and strong dependencies within the existing code?

A shared deployment with clear module boundaries is an option worth considering when the domains are mostly changed together. Microservices are worth considering when a distinct business domain has a clear need for independent releases or separate scaling and the team can handle the additional operational work.

For a rebuild, a limited candidate with clear responsibility is advisable. Before extraction, teams should define the interface, data ownership, failure behaviour and metrics for the expected benefit. They can then assess actual operations to determine whether further separation makes sense or whether the shared application is a better fit.

Frequently Asked Questions

When are microservices worthwhile?

They are worth considering when distinct business domains need to be deployed or scaled independently and the benefits justify the additional operational complexity.

What is a modular monolith?

A jointly deployed application whose business domains are organised as modules with defined interfaces. The quality of the boundaries depends on their design and maintenance.

When should services be combined?

A review is worthwhile when services are frequently changed together or communicate extensively with one another. Microsoft cites such dependencies as a possible reason to redraw boundaries or combine services.

Image source: AI-generated (November 2026)

Translated from the German original using artificial intelligence. The German version is authoritative.

Also available in

FrançaisEspañolDeutsch
MBF Media Newsletter

The monthly briefing for decision-makers

Once a month, the MBF Media Newsletter gathers what matters from cloudmagazin, MyBusinessFuture, Digital Chiefs and SecurityToday, curated by the editorial team.

Around 23,500 IT and business decision-makers read this newsletter. Read along.

Subscribe for free
MBF Media Newsletter, aktuelle Ausgabe auf dem iPhone
A magazine by Evernine Media GmbH