Skip to content
Module
Tech

What is a modular monolith? Definition and benefits

A modular monolith is an application shipped as one deployable whole but organized into independent modules, each owning a business domain such as billing, catalog or accounts. Modules talk to each other through explicit interfaces and do not reach directly into each other's data. You keep the operational simplicity of a monolith while keeping the code from turning into a tangle.

Definition written by Alex Dionisio, Senior Product Manager. Updated November 13, 2026.

Why it matters for a PM

Architecture choices affect delivery speed, infrastructure cost and the team size you need. For many products, a modular monolith lets a small team move fast without the networking and operational overhead of microservices. If a module ever needs to become a separate service, its clean boundaries make the extraction far easier.

Example

A booking startup is tempted to begin with microservices to be ready for growth. With six engineers, the team picks a modular monolith instead: bookings, payments and notifications are separate modules in one repository. Two years later, only the heavily used notifications module is extracted into its own service.

Key points

  • One deployment and one codebase, with internal boundaries that are respected.
  • Each module owns its data and exposes what the others need.
  • Testing and debugging stay simpler than with services spread across a network.
  • It is often a sensible stage before extracting a few services, if ever needed.

Common mistakes

  • Confusing a modular monolith with old monolithic code that has no structure.
  • Letting modules read each other's tables directly, which brings back the tangle.
  • Choosing microservices because they are fashionable rather than for a measured need.

Go further with Module

The courses and lessons that cover this concept:

Guide on this topic