Effective Measures to Minimize Rollbacks
Question
You need to reduce the number of unplanned rollbacks of erroneous production deployments in your company's web hosting platform.
Improvement to the QA/ Test processes accomplished an 80% reduction.
Which additional two approaches can you take to further reduce the rollbacks? (Choose two.)
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D. E.AC.
The 80% reduction achieved through improvement in the QA/Test processes is commendable, but there are still two additional approaches that can be taken to further reduce the number of unplanned rollbacks of erroneous production deployments. These are:
A. Introduce a green-blue deployment model: This approach involves having two identical environments for the platform, one that is currently live (blue environment) and another that is inactive (green environment). When a new deployment is ready, it is first deployed to the green environment where it can be tested and verified before traffic is switched over to it. This approach reduces the impact of any errors or issues that may arise during deployment since traffic is still being served by the currently live environment. If any issues are identified during testing, the deployment can be rolled back without any impact on users. Once the green environment is verified to be working correctly, traffic is switched over to it, and the blue environment becomes the inactive one. This approach is particularly useful for high-traffic applications where downtime during deployments is not acceptable.
B. Replace the QA environment with canary releases: In this approach, new deployments are first released to a small subset of users (usually 1-5%) before being released to the entire user base. This allows for any issues to be identified and resolved before the deployment is released to everyone. If any issues are identified, the deployment can be rolled back before it affects the entire user base. This approach reduces the risk of deploying faulty code to the entire user base and helps identify issues before they become widespread.
C. Fragmenting the monolithic platform into microservices could improve the overall reliability of the platform, but it may not necessarily reduce the number of unplanned rollbacks of erroneous production deployments. Fragmentation may introduce new challenges in managing and deploying the microservices.
D. Reducing the platform's dependency on relational database systems could improve the platform's scalability and performance, but it may not necessarily reduce the number of unplanned rollbacks of erroneous production deployments.
E. Similarly, replacing the platform's relational database systems with a NoSQL database could improve the platform's scalability and performance, but it may not necessarily reduce the number of unplanned rollbacks of erroneous production deployments.
In summary, the most effective approaches to reduce the number of unplanned rollbacks of erroneous production deployments would be to introduce a green-blue deployment model and replace the QA environment with canary releases.
