Comparison
Blue-green deploymentvsCanary deployment
Blue-green deployment
you stand up a complete second environment on the new version and switch all traffic to it at once.
Running two full environments and cutting traffic from the old to the new in one step, with the old kept warm for rollback. Rollback is a traffic switch, which is as fast as it gets. It doubles infrastructure for the duration and does not help with shared state: the database is still singular and still migrated.
Full entry →Canary deployment
the new prompt goes to two percent of traffic first, and you watch quality and cost before letting the rest through.
Rolling a prompt or model change to a small traffic slice first, watching quality and cost metrics, then widening. Treat prompts as deployable artefacts with the same ceremony as code, because they break things the same way.
Full entry →