Available now
System Design
From the first request to the trade-offs at scale. Read the concepts, break a simulation, and explain your decisions.
Explore System Design ↗A learning platform for engineers
Learn system design by connecting ideas, experimenting with real systems, and recalling what matters.
Next up
DraftContinue Explore Skilltree ↓Saved progress is unavailable on this visit. You can still explore every topic.
Not read Read Review due
Topics & prerequisites ↓Branches show what to read first. Every topic is open to explore.
Start with what is here.
More ways to grow are taking shape.
Available now
From the first request to the trade-offs at scale. Read the concepts, break a simulation, and explain your decisions.
Explore System Design ↗More pathsNot available yet
Read. Experiment. Recall. Review.
Make each idea earn its place.
Read the concept and see which ideas it builds on.
Read about caching →Move a parameter. Predict what happens. Test the trade-off.
Try cache eviction →Test what you remember before looking at the explanation.
Test yourself →Quiz questions include Draft contentReturn to seen flashcards when the scheduler says they are due.
Open flashcards →The systems are the proof
What happens when one server leaves a hash ring? Try it here. Only the keys that need a new owner move.
Open Consistent hashing ↗The same deterministic model as the full lab. One ring point per server; 5,000 example keys. A model, not a production benchmark.
A key belongs to the next server clockwise. Open the full lab for virtual nodes and replicas.
December revenue by category · query & recording
PostgreSQL 18.6 (PGlite 0.5.9)
Read inside out: children do their work before passing rows to their parents.
Real queries. Real output.
This is a recorded PostgreSQL execution plan, not a picture of one. Follow each operation from table scans to the final result.
21 database pages · 12 tuning exercises Draft
Explore databases ↗Recorded rows and estimates come from the site’s own SQL run. They describe this query and dataset, not every database.
Browse the full map. Prerequisites are suggestions, never locked doors.
Before this: Domain name system
Before this: Domain name system
Before this: Load balancer
Before this: Load balancer
Before this: Application layer
Before this: Availability patterns, Latency vs throughput
Before this: Consistency patterns
Before this: Database