deployment-patterns

Blue-green deployment switches traffic between two identical environments, whereas canary deployment gradually routes a subset of users to the new version. The Skill details both strategies, explaining their pros and cons for web application releases.

To write a multi-stage Dockerfile, you separate the build environment from the final production image. This Skill provides multi-stage Dockerfile examples for Node.js, Go, and Python to optimize containerization and reduce final image size.

You configure Kubernetes probes by defining health check endpoints in your application and setting up liveness and readiness probes in your deployment manifests. This Skill details implementation for production readiness and rollback safety.

The best way to set up a CI/CD pipeline involves automating build, test, and deployment stages. This Skill provides a standard GitHub Actions workflow example to streamline continuous integration and delivery for web applications.

Implementing a safe rollback procedure requires having deployment strategies like blue-green or canary in place, along with production readiness checklists. This Skill includes strategies and checklists for safely reverting failed releases.

Yes, the deployment guidance emphasizes the Twelve-Factor App pattern for environment configuration. It covers configuration validation and separation of config from code to ensure production readiness across different environments.