liveBook · Manning

Distributed monolith

A distributed monolith is a system whose separately deployed components remain tightly coupled, retaining the coordination and evolution constraints of a monolithic application.

How 2 Manning books explain it

Microservices Patterns, Second Edition

A distributed system whose services remain tightly coupled and therefore retain the disadvantages of a monolith.

How it is used
Warns that tightly coupled services can combine the disadvantages of monolithic and distributed systems.
How deep it goes
Defines the failure and links its avoidance to independent deployability, loose coupling, stable APIs, and monolith-first development.
Examples
Uses a createOrder operation spanning Order and Customer services to illustrate distributed-operation complexity.
What you can do after
Evaluate whether service boundaries and APIs support independent deployment, or whether a monolith is the simpler starting point.

Read how Microservices Patterns, Second Edition explains distributed monolith →

Grokking Software Architecture

A distributed monolith is a system whose deployable units are separated across processes or machines but remain tightly coupled through shared data or synchronous call chains.

How it is used
Warns against splitting deployable services without removing their logical coupling.
How deep it goes
Defines the pattern, explains shared-database and synchronous-call failures, and traces their operational costs.
Examples
Uses an order workflow that calls inventory, payment, and shipping services, plus a shared SQL database scenario.
What you can do after
Evaluate whether service boundaries actually reduce coupling and recognize how synchronous chains spread failures.

Read how Grokking Software Architecture explains distributed monolith →

Also covered in

What to know first

Related concepts

Questions about distributed monolith

What is distributed monolith?

A distributed monolith is a system whose separately deployed components remain tightly coupled, retaining the coordination and evolution constraints of a monolithic application.

Which Manning books explain distributed monolith?

Microservices Patterns, Second Edition and Grokking Software Architecture.

What should I know before learning distributed monolith?

Manning books that teach distributed monolith usually introduce distributed system, Fallacies of Distributed Computing and scalability first.

What is the difference between distributed monolith and modular monolith?

A distributed monolith is a system whose separately deployed components remain tightly coupled, retaining the coordination and evolution constraints of a monolithic application. A modular monolith is an application deployed as a single unit and internally organized into distinct modules with defined boundaries and controlled dependencies.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.