Designs

Pick a system. Work through the problem. Compare your approach.

Create your own

All designs 10

Ordered by design number

Company tags are community-reported. Counts on cards show how many people reported that design.

Distributed systemsClear filters

2. Design a Distributed Rate Limiter
Enforce tenant quotas across servers while making burst behavior and outage policy explicit.
ClassicMedium
Caching Databases Concurrency
+8
Distributed systems API gateways AWS Lua Rate limiting Redis Reliability Token bucket
Worked design
Practice
3. Design a Distributed Cache
Partition cached data, survive node loss and keep cache misses from overwhelming the source of truth.
ClassicMedium
Caching Sharding Databases
+9
Distributed systems AWS Consistency Consistent hashing Hot keys LRU eviction Memcached Redis Replication
Worked design
Practice
11. Design a Container Orchestrator
Reconcile desired workloads, schedule containers and recover from failed nodes safely.
ClassicHard
Distributed systems AWS Control plane
+6
etcd Isolation Kubernetes Orchestration Reconciliation Scheduling
Worked design
Practice
Practice briefStart with your own approach
13. Keep a regional ingress service alive
Survive a regional outage without confusing a health check with safe recovery.
Infrastructure & SREHard
Distributed systems Capacity planning Failover
+3
Multi region Reliability Routing
Discuss
Practice
42. Design a Metrics Monitoring Platform
Collect 5 million samples a second from 500,000 hosts, store them as time series, chart them and page people.
ClassicMedium
Databases Streaming Observability
+7
Distributed systems Alerting AWS Cardinality Kafka Prometheus Time series
Worked design
Practice
67. Design for Write Scale: A Million Writes a Second
A live TV vote at a million writes a second: spread by key, buffer in Kafka, aggregate the hot counter in two stages, shed what can wait.
ClassicMedium
Sharding Databases Streaming
+6
Distributed systems AWS DynamoDB Flink Kafka Scaling writes
Worked design
Practice
70. Design an In-Memory Data Store like Redis
An in-memory data store like Redis, from one event loop to Redis Cluster to a durable platform.
ClassicMedium
Caching Sharding Databases
+5
Distributed systems AWS In memory Redis Replication
Worked design
Practice
78. Design a Coordination Service like ZooKeeper
A coordination service like ZooKeeper: znodes, sessions and watches, a ZAB quorum of five with observers, and the recipes for elections and locks.
ClassicMedium
Concurrency Distributed systems AWS
+5
Consensus Coordination Distributed locks Leader election ZooKeeper
Worked design
Practice
97. Design a Distributed Logging and Error Tracking System
Ten terabytes of logs an hour from host agents through Kafka into tiered OpenSearch and S3, with regex search, live tail and exceptions grouped into issues.
ClassicMedium
Streaming Search Observability
+7
Distributed systems AWS Error tracking Flink Kafka Logging OpenSearch
Worked design
Practice
100. Design a Distributed File System
Billions of files, hundreds of petabytes, one strongly consistent tree: a namespace partitioned by directory, chunk servers, replication, repair, erasure coding. One-hour boards for junior, senior and staff, with the theory behind them.
ClassicMedium
Databases Distributed systems AWS
+6
DynamoDB Erasure coding File system Infrastructure Replication Storage
Worked design
Practice

Each design brings together the brief, practice, examples and discussion.

All designs 10

2. Design a Distributed Rate Limiter

3. Design a Distributed Cache

11. Design a Container Orchestrator

13. Keep a regional ingress service alive

42. Design a Metrics Monitoring Platform

67. Design for Write Scale: A Million Writes a Second

70. Design an In-Memory Data Store like Redis

78. Design a Coordination Service like ZooKeeper

97. Design a Distributed Logging and Error Tracking System

100. Design a Distributed File System