CompTIA DataSys+ (DS0-001)Database Management and MaintenanceMedium
A database administrator is planning a significant database schema change that involves adding several new columns and modifying existing data types in a large production table. To minimize downtime and ensure data consistency during the deployment, they decide to use a phased approach where the old and new schema versions coexist for a period. Which deployment strategy are they employing?
- ARolling deployment.
- BCanary deployment.
- CBlue/Green deployment.
- DBig Bang deployment.
Show answer & explanationAnswer & explanation
Correct answer: A. Rolling deployment.
Rolling deployment involves gradually updating applications or database components in phases, allowing old and new versions to coexist temporarily. This minimizes downtime and risk by slowly transitioning users/traffic from the old to the new version.
Why the other options are wrong
- B. Canary deployment gradually rolls out changes to a small subset of users to test in production before a full rollout, often used for application features, but less directly for database schema changes co-existing.
- C. Blue/Green deployment involves running two identical production environments (Blue and Green) and switching traffic between them, which is more for application instances than gradual schema changes on a single database.
- D. Big Bang deployment involves deploying all changes at once, leading to significant downtime.
Rolling Deployment
A deployment strategy where application or database components are updated incrementally, instance by instance or in small batches, allowing the old and new versions to coexist and serve traffic during the transition.
- Minimizes downtime by avoiding a complete system shutdown.
- Allows for gradual introduction of changes.
- Requires backward compatibility between old and new versions during the transition.
Memory trick: Roll out the changes one step at a time, like a red carpet.