Whole systems / 1 / 4
From requirements to design
How to approach a design task without jumping to boxes. One small system, a city bus arrival board, goes through requirements, rough numbers, a high-level picture and then a detailed design of one part, with the trade-offs written down.
- 13 min
- Beginner
- 11 steps
- Positions in
- —
- Rider requests
- —
- Answer p95
- —
- ETA age
- —
- request
- reply
- redelivery
- duplicate
- lost
Numbers are a model scenario, not measurements
The real request
Bus GPS unit → Arrivals APIRequest
POST /positions HTTP/1.1
{
"bus_id": 1"b_17",
"route": 2"R11",
"lat": 41.3111,
"lon": 69.2797,
"ts": 31795421720
}
Response
HTTP/1.1 204 No Content
bus_id— Which bus. Each of about 800 buses has its own.route— The line the bus serves now. Riders care about routes, not buses.ts— When the GPS fix was taken, in seconds. Old positions must not overwrite new ones.
Course: 42 lessons
01 Foundations
02 Scaling
03 Data & storage
04 Communication
05 Reliability
06 Architecture
07 Security
08 Shipping
09 Whole systems
10 Business processes