liveBook · Manning

Distributed monolith

As explained in Microservices Patterns, Second Edition

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

A distributed monolith is an application split across tightly coupled services, combining disadvantages of monolithic and distributed systems. Microservices need independent deployability and loose coupling to deliver their promised benefits. section 7.3 section 7.7

Unstable service boundaries and APIs can create this risk. For a new application, boundary and API changes are often easier in a monolith; start with one unless multiple technologies or compelling segregation needs justify services. section 1.4.1

Service-spanning operations also bring network latency, partial failure, and eventual consistency. Treat those costs as design constraints when deciding whether to distribute an application. section 1.3.4 section 7.7

How Microservices Patterns, Second Edition covers it

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.
How it connects
Connects microservice architecture with independent deployability, loose coupling, stable APIs, monolithic architecture, and eventual consistency.

Also explained in

Compare how 2 books explain distributed monolith →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.