online
← Back to notes

> less ./notes/backend-under-load.md

Backend under load starts with boring questions

Patterns for APIs, queues and data: when a monolith is faster and where event-driven loops become necessary.

backend-under-load.md field: backend / queues / data boundaries

field: backend / queues / data boundaries

Load rarely starts with abstract architecture. First you need to understand real scenarios, data boundaries, background jobs and places where a simple synchronous model stops being honest.

Only then do queues, read models, event-driven loops and separate services appear. Otherwise architecture becomes expensive decoration.