← All comparisons
Open Ticketmaster (Seat Booking) →Open URL Shortener →

Ticketmaster (Seat Booking) vs URL Shortener

Ticketmaster (Seat Booking)

Ticketmaster (Seat Booking)

Seat holds, payment timeouts, virtual queue for hot events.

Components (8)

  • Browser / Mobile
  • Virtual Queue
  • API Gateway
  • Booking Service
  • Seat Locks
  • Postgres
  • Postgres
  • Stripe

Headline numbers

  • Seat reservation QPS at peak drop~10K/sec
  • Virtual queue depth at peakUp to 500K
  • Steady-state seat ops<100/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 Ticketmaster (Seat Booking)
  • Virtual Queue
  • Stripe
In both
  • Client
  • Api Gateway
  • Service
  • Cache
  • Database
Only in URL Shortener
None.

Flow shape

Ticketmaster (Seat Booking) flows
  • Buy a ticket (happy path)7 steps
  • ⚠ User abandons checkout4 steps
  • Hot event drop: millions hit at once2 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