MonolithFirst

Martin Fowler · 3 Jun 2015 · martinfowler.com ↗

3 korrents from this piece

Martin Fowler did not write this page.

Every claim below was made in this piece, quoted word for word and numbered in the order the piece makes them, so you can read it there rather than take our word for it. The sentence above each quote is our reading of the claim, not their wording. Each quote was checked against a stored copy of the page at build time; where the two differ, the quote is the fact.

Our reading
Successful microservice systems almost always began as a monolith that grew too big, and systems built as microservices from scratch end up in serious trouble.

Their wordsAlmost all the successful microservice stories have started with a monolith that got too big and was broken up

Interesting
Our reading
Build a new application as a monolith first, even when you are confident it will eventually need microservices.

Their wordsThis leads to a powerful argument for a monolith-first strategy, where you should build a new application as a monolith initially, even if you think it's likely that it will benefit from a microservices architecture later on.

Interesting
Our reading
Service boundaries cannot be got right at the start, and moving functionality between services is far harder than moving it inside a monolith.

Their wordsBut even experienced architects working in familiar domains have great difficulty getting boundaries right at the beginning.

Interesting