Architecture lab

Challenge 16: Losing a zoneTarget 20,000 RPS

0% busy
Users
1x inst20,000 RPS
67% busy
Load balancer
6x inst20,000 RPS
67% busy
Application servers
30x inst20,000 RPS
26% busy
Memory cache
6x inst19,000 RPS
12% busy
Database
6x inst2,900 RPS

Design summary

Components

  • Users: 1 × Users
  • Load balancer: 6 × Load balancer, 20,000 requests a second, 67% busy
  • Application servers: 30 × App server, 20,000 requests a second, 67% busy
  • Memory cache: 6 × Cache, 19,000 requests a second, 26% busy
  • Database: 6 × NoSQL store, 2,900 requests a second, 12% busy

Connections

  • Users sends requests to Load balancer
  • Load balancer sends requests to Application servers
  • Application servers sends requests to Memory cache
  • Memory cache sends requests to Database
  • Application servers sends requests to Database

20,000 of 20,000 requests a second served, average 21 ms, p99 57 ms, 3,210 USD a month. Challenge not yet passed: losing a zone.