← All comparisons
Open Uber (Driver Matching) →Open URL Shortener →

Uber (Driver Matching) vs URL Shortener

Uber (Driver Matching)

Uber (Driver Matching)

Geo-indexing, dispatch, real-time location streams.

Components (9)

  • Rider App
  • Driver App
  • API Gateway
  • Dispatch
  • Trip Service
  • Kafka
  • Geo Index
  • Postgres
  • Cassandra

Headline numbers

  • Location pings / sec~250,000/sec
  • Dispatch queries / sec~5,000/sec
  • Matches / sec~1,000/sec
URL Shortener

URL Shortener

Hashing, key generation, read-heavy caching.

Components (6)

  • Client
  • API Gateway
  • Write Service
  • Read Service
  • Redis
  • Postgres

Headline numbers

  • Write QPS (avg)~1,200/sec
  • Read QPS (avg)~120,000/sec
  • Storage per year~5 TB

Key differences

Only in Uber (Driver Matching)
  • Kafka
In both
  • Client
  • Api Gateway
  • Service
  • Cache
  • Database
Only in URL Shortener
None.

Flow shape

Uber (Driver Matching) flows
  • Request a ride7 steps
  • Driver location update4 steps
  • ⚠ Geo Index is down4 steps
URL Shortener flows
  • Shorten a URL3 steps
  • Resolve short URL (cache hit)3 steps
  • Resolve short URL (cache miss)4 steps
  • ⚠ Redis is down4 steps