Queues and messaging: asynchronous processing and decoupling
Don't block the request waiting: how queues and messaging decouple services, absorb load spikes and make asynchronous processing reliable.
What a back-end engineer needs to master at each stage of their career. From the first HTTP request to distributed architecture — the concepts that come up in technical interviews and in everyday work, explained directly. Filter by level below.
No articles found for your search.
Don't block the request waiting: how queues and messaging decouple services, absorb load spikes and make asynchronous processing reliable.
What really happens between typing a URL and the page showing up — DNS, request, response and the cycle that underpins every back-end.
Resources, verbs, status codes and statelessness — the API vocabulary every back-end uses and every interview asks about.
How to talk to a relational database: the four operations, the types of JOIN and why transactions exist (ACID without the pain).
Who you are (authentication) and what you can do (authorization). Sessions, JWT tokens and OAuth explained without the mystery.
The hidden query that multiplies database access and tanks performance — how to spot it and fix it with eager loading.
Caching speeds everything up — until it becomes a source of bugs. Cache-aside, TTL and why cache invalidation is one of the hard problems in computing.
Grow up or grow out? Stateless, load balancers and the limits of each strategy when traffic explodes.
Why distributed systems force you to choose between consistency and availability when the network fails — explained with examples.
Failures will happen. How to design a back-end that survives them: idempotency, retry with backoff and the breaker that prevents the domino effect.
Check what you already master. Your progress is saved in this browser only.
Four questions per level, with an explanation and the article that covers each topic. Ace a level and you can mark it in the self-assessment above.