Our reading notes

The Death of Microservice Madness in 2018

Article by Dave Kerr

A detailed discussion of why microservices appeal, where their operational costs appear, and what to ask before splitting a system.

What to look for

01
Connect proposed service boundaries to concrete development or scaling needs.
02
Include deployment, debugging, and coordination costs in the decision.

Keep in mind

A historical 2018 argument. The title is rhetorical; it is neither evidence that microservices disappeared nor a rule against them.

Put it to work

Try this next

Write the problem a proposed split solves and the new operational responsibilities it creates.

Get the architecture template

Notes and exercises by Awesome CTO. The original work belongs to Dave Kerr.

Work through the bigger question.

Our architecture guide connects the reading to a practical approach and a template.