Problem context and objectives
Lead systems engineer · Dispatch Observatory
Design observability for a ride-dispatch service that matches riders and drivers across cities in real time.
The design must survive locations 1M updates/s and matches 20K/s. Every box must earn its place by satisfying a requirement or containing a failure.
How you win
- 1Trace one user action from request to durable outcome
- 2Connect every component to a stated requirement
- 3Explain the losing tradeoff, not only the chosen technology
Rules and pressure
- locations: 1M updates/s
- matches: 20K/s
- User-centered SLOs
- Traceable match lifecycle
New words in this mission
Open a term for a plain-language explanation.SLO+
A measurable reliability target, such as 99.9% successful requests in 30 days. It turns 'reliable' into a promise the team can check.
Live architecture trace
Dispatch Observatory: request to outcome
Rider + driver sends “updates” to Regional gateway. A user-visible success and latency SLI anchors observability to the product promise.
Design observability for a ride-dispatch service that matches riders and drivers across cities in real time. Follow one real user action through the complete architecture; a component is useful only when you can explain the request, state, or failure it handles.