Our reading notes

The Reactive Manifesto

Manifesto by Reactive Manifesto authors & signatories

A concise statement of responsive, resilient, elastic, message-driven systems, with a glossary for discussing these architectural qualities.

What to look for

01
Translate each quality into behavior your users or operators can observe.
02
Distinguish the system properties from a particular reactive-programming library.

Keep in mind

A manifesto expresses design goals, not proof that an implementation meets them or that every system needs the same architecture.

Put it to work

Try this next

Choose one claimed quality and describe a failure test that would show whether your service actually provides it.

Get the architecture template

Notes and exercises by Awesome CTO. The original work belongs to Reactive Manifesto authors & signatories.

Work through the bigger question.

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