Blue and green

  • Order
  • Guard 15

Difficulty 3 of 5

Blue serves production. Green uses the same compatible data schema. Tests pass, but errors rise after the switch. Put the release and rollback steps in order. Keep blue ready until green is proven.

Play level

Put these steps in order

  • Send new production traffic to green; keep blue ready
  • Drain or stop remaining green requests before removal
  • Observe the higher error rate on green
  • Deploy green while blue serves production
  • Send new production traffic back to healthy blue
  • Test green without moving production traffic
A canary before the whole fleetTap to change the deployment method

Goals and limits

p99 latency
under 200 ms
Monthly cost
under 10 USD/mo
Traffic
100 req/s

Concepts

How players did

Player results load from the server.