ShelfSoftware Engineer (Backend)
Microservices · Intermediate · 8 h
Services, events and failure
Service boundaries, synchronous and asynchronous communication, the outbox pattern, idempotent consumers, timeouts, retries and circuit breakers.
Why employers care: Engineers on microservice teams must reason about partial failure and duplicate messages. These are standard interview topics for mid-level backend roles.
In the roadmaps for: Software Engineer (Backend)
Lessons, in order
- Service boundaries, events and the outbox patternDecide where to split services, choose between calls and events, and publish events reliably without losing or double-counting them.4 min
- Timeouts, retries and circuit breakersStop one failing service from taking down the others, and watch a circuit breaker fail fast and then recover.5 min