Deployment Projects: Blue-Green and Rolling Deployments Without the Operational Overhead

The most stressful moment in most engineering teams' week is production deploy time. Someone has a finger hovering over a rollback script. Someone else is watching error rates in Datadog. The on-call engineer is on Slack. None of this is necessary. QuickInfra's Deployment Projects are designed to make production deployments something you do without thinking twice.

What Is a Deployment Project?

A Deployment Project in QuickInfra handles the application layer — deploying new versions of your software onto existing infrastructure. It's separate from Infrastructure Projects by design: your VPC, EC2 instances, and load balancer change infrequently, but your application code changes daily. Deployment Projects manage that fast-moving layer independently.

Blue-Green Deployments

With a blue-green deployment, QuickInfra maintains two identical environments — blue (live) and green (standby). When you trigger a deploy, the new version goes to the green environment. QuickInfra runs health checks against green. Once it passes, traffic is shifted from blue to green at the load balancer level — typically in under a second. The old blue environment stays up for a configurable cool-down period, giving you an instant rollback path if something unexpected surfaces post-deploy.

The cost implication is minimal: the standby environment runs at a reduced capacity during idle periods and scales up only during the deployment window.

Rolling Deployments

For workloads where running two full environments isn't practical, rolling deployments update instances in batches. QuickInfra takes a configurable percentage of instances out of rotation, deploys the new version, runs health checks, then proceeds to the next batch. If any batch fails health checks, the deployment halts and the remaining instances stay on the previous version — giving you a partial rollout with an automatic stop gate.

Deployment History and Audit Trail

Every deploy is recorded: who triggered it, what version was deployed, what the diff was from the previous version, how long it took, and whether it succeeded or was rolled back. This audit trail is queryable from the console and can be exported for compliance purposes. For teams working under SOC 2 or ISO 27001, this is change management documentation generated automatically.

Rollback in One Click

QuickInfra retains the previous deployment artefact and configuration. If a bad deploy makes it to production, you can roll back to the last known good version from the console in a single click. The platform runs the same health check process on rollback that it ran on deploy — no shortcuts, no skipped validation.

Connecting a Deployment Project to Your Pipeline

Deployment Projects can be triggered manually from the console or automatically as the final stage of a CI/CD Pipeline project. The handoff is clean: the pipeline builds and tests your artefact, then triggers the Deployment Project with the new artefact version. The deployment runs with the same visibility and control as a manual deploy.