Complete AWS CI/CD study guide for DVA-C02. CodeCommit, CodeBuild, CodeDeploy (deployment strategies), and CodePipeline. Includes blue/green, canary, rolling deployments and common exam patterns.
AWS CodeDeploy deep dive for DVA-C02. Deployment groups, lifecycle hooks, rollbacks, appspec.yml for EC2, Lambda, and ECS, blue/green deployments, deployment configurations, and traffic shifting strategies.
Elastic Beanstalk for DVA-C02. Deployment policies (All at once, Rolling, Rolling with additional batch, Immutable, Blue/Green), .ebextensions, .platform, environment tiers, database decoupling, and Java Spring Boot deployment.
Deep dive into Blue-Green Deployment — zero-downtime releases, instant rollback, Kubernetes implementation, database migration compatibility (expand-contract), CI/CD pipeline integration, and comparison with canary and rolling updates.
Components are the units of deployment — JARs, DLLs, shared libraries. Martin traces their history from early relocatable binaries to modern package managers, establishing the foundation for the component cohesion and coupling principles that follow.
A comprehensive guide to managing and verifying application configurations, environment variables priority, HashiCorp Vault secrets, Kafka topics, ACLs, schema registry compatibility, database migrations, and post-deploy health verification.
Deep dive into Feature Toggles — 4 toggle types, trunk-based development, percentage rollout, A/B testing, LaunchDarkly vs DB-backed implementation, toggle debt, and testing strategies.
Lambda Layers, Versions, and Aliases for DVA-C02. Layer structure, sharing across functions, version immutability, alias routing for canary deployments, and $LATEST vs published versions.
The **Deployment phase** moves tested, approved software from the staging environment to production. A well-executed deployment is **planned, automated.
**Roll-backward** (commonly called a **rollback**) is a deployment recovery strategy where the system is reverted to the **previously known-good version** when.
**Roll-forward** is a deployment recovery strategy where, instead of reverting to the previous version when an issue is detected, the team **fixes the defect.
Complete guide to Kubernetes workload resources — Deployments, ReplicaSets, StatefulSets, DaemonSets, Jobs, and CronJobs with rolling updates, rollbacks, and autoscaling.
