Skip to slide
193 / 221

CH 16 · Scaling and Infrastructure · 10/11

Read as one page

Deployment and operational basics

  • Containerize so the runtime (including any subprocess dependencies like a document converter) is reproducible.
  • Health checks so the load balancer routes only to healthy instances.
  • Horizontal autoscaling on the stateless web tier based on connections/CPU; separate scaling for workers based on queue depth.
  • Config via environment (secrets in a manager; Chapter 12), so the same image runs in every environment.
  • Observability and alerting (Chapter 15) so you see saturation and failures before users do.

Finished this idea?

Your learning progress stays in this browser.