Pub/Sub vs Message Queues: Architecture, Delivery Guarantees, and Scaling Patterns
Pub/Sub vs Message Queues decides if many readers share one event or one worker owns a task. Learn…
Category
These system design guides cover how to build software that scales and stays up. There are over a hundred posts, grouped by topic.
For a start, read load balancing and caching. Then high availability covers uptime. Also, each sub section goes deeper into one area.
112 articles
Pub/Sub vs Message Queues decides if many readers share one event or one worker owns a task. Learn…
Rollback Strategies for Backend Systems cover code, config, and data. Learn blue-green, canary, and when a database change…
JWT Rotation and Revocation keeps distributed APIs safe after a key leak. Learn short lifetimes, key ids, denylists,…
Database Migrations at Scale need expand and contract steps. Learn how to change schemas with no downtime, keep…
Blue green vs canary deployment decided: zero downtime deployment mechanics, the canary release strategy and its observation ramp,…
Clock Skew in Distributed Systems breaks leases, caches, and event order. Learn the causes, the impact on reads,…
Health Checks in Distributed Systems tell a platform if a task can serve traffic. Learn liveness, readiness, and…
Retry with exponential backoff explained: backoff and jitter pacing, the retry storm math, retry budgets, what is safe…
Cron Jobs in Distributed Systems must run once, survive restarts, and stay idempotent. Learn locks, missed runs, jitter,…
Query Optimization for Backend Engineers stops slow SQL from stalling APIs. Learn indexes, plans, and safe fixes you…
N+1 Queries hide inside ORM loops and then spike the database at peak load. Learn how to detect…
Disaster recovery explained: RTO and RPO as the two numbers that size the plan, the disaster recovery strategies…
Read Replicas cut read load, but lag can show stale rows to real users. Learn routing rules, lag…