Explain like I'm five · SW Eng

What is Microservices Architecture (MSA)?

Microservices architecture, told as a story about splitting one thick encyclopedia into small standalone volumes — animals, history, science — each written and printed on its own.

fixing even one chapter means reprinting the entire encyclopediaif one part falls behind, the whole book's release falls behind too

Fixing even a single typo means reprinting the entire encyclopedia.If one part falls behind, the whole book's release falls behind too.

just write faster to make the deadlineit's all one bound book — no part can ship alonewhen the whole book is bound together, there's no way to release just part of it early

The editor says write faster; the writer answers that everything's bound into one book, so no part can ship alone.When the whole book is bound together, there's no way to release just part of it early.

animalshistorysciencemicroservices architecture = splitting one thick book into small standalone volumes, each written and printed independentlythe volumes only point to each other through a shared index — they never mix content

Microservices architecture splits one thick book into small standalone volumes.The volumes only point to each other through a shared index — they never mix content.

Split it smalldividing it into standalone volumes
Give each its own teameach volume has its own dedicated team
Connect only through the indexnever mixing the content
Grow each on its ownreprinting only the popular volume
TRAITS OF THE SPLIT STRUCTUREindependent release — one volume can ship aloneindependent teams — each volume has its own teamlinked by index — refers via contents page onlyseparate sizing — reprint just the popular volumethe more volumes, the more indexes to coordinatethe split structure can be more than a small publishing house can handle

The split structure has four traits: independent release, independent teams, index-only links, and separate sizing.The more volumes, the more indexes to coordinate.

split well, a problem in one volume spreads lessbut the cost of coordinating the index goes upmicroservices trade away being bound together — but create a new job: coordination

Splitting the book into volumes creates a new job: coordination.The split structure's benefits are paid for with coordination costs.

In one breath

Microservices architecture = splitting one thick book into independent standalone volumes, linked only through a shared index.

Microservices architecture splits one giant application (a monolith) into small services that can each be developed, deployed, and scaled independently. Services communicate only through defined channels such as APIs or messages, hiding their internal implementation from each other. A failure or traffic spike can stay contained to one service, but as services multiply, the cost of coordinating and operating them all grows too.

When grown-ups say it

Microservices Architecture
A structure split into independent volumes. Each service deploys and scales on its own.
Monolith
One thick, bound-together encyclopedia. What microservices architecture splits apart.
API
The index the volumes use to point to one another. Refers without mixing content.
Independent Deployment
Being able to print one volume alone, first. A monolith usually deploys as a whole.
Service Mesh
The dedicated path between the volumes. A dedicated layer handling communication between the volumes. → the dedicated path between rides
API Gateway
The single front desk readers always go through. A single window set up in front of many volumes.
Software Architecture Model
The big framework that decides a book's overall shape. Microservices is just one of those models. → the blueprint that shapes the whole book ahead of time
IS Audit/PMO
The checker who watches the whole publishing run. The more volumes there are, the more places audit has to check. → the checker who watches the whole publishing run
Next story
The Design Map Drawn Before Writing →
Want another term as a picture book? Request →