Description
Compare and contrast three DevOps deployment strategies from three separate literatures of your choice from AWS five deployment strategies. Reference can be found below
https://docs.aws.amazon.com/whitepapers/latest/introduction-devops-aws/deployment-strategies.html
Explanation & Answer
Attached.
1
COMPARE AND CONTRAST THREE DEVOPS DEPLOYMENT STRATEGIES
DEPLOYMENT TYPE 1: CANARY RELEASE.
Literature
A canary release means that a change is slowly rolled out to a few users before it spreads across
the infrastructure and becomes available to all users.1 Canary release is similar to a blue/green
rollout in that a new version of your software is rolled out to a subset of the infrastructure
whose users are not the target audience.
Strategies for selecting which users will see the new version include a simple random selection
strategy, releasing the new version to your internal users and employees before it is rolled out
to the world, and selecting users based on their profile and factors such as demographics.1
Developers can start releasing a new version on more infrastructure servers and target more
users as they gain confidence in the new version. To properly deploy a new version, a developer
must either move existing infrastructure to Phoenix servers or create new infrastructure and
decommission the old infrastructure into unmodified servers.
Different allocation strategies are usually used in large distributed scenarios instead of
determining which users should be migrated to the new version. For example, for
geographically distributed users, developers might roll out to a region or a specific location
first; if you have multiple brands, you might roll out to one brand first.1 A good example is
Facebook, which uses a multi-channel strategy. The strategy is designed so that the first one is
visible only to their internal staff and has all features enabled so that problems can be detected
early enough.
Highlights.
Some strategies for deploying canary versions emphasize the possibility of evaluating multiple
versions of services side-by-side with canary deployments in natural environments with real
1
2
users and usage scenarios. This strategy is cost-effective because only one production
environment is needed and is cheaper than the blue-green deployment strategy.
Canary deployment offers several benefits to businesses.1 It allows companies to test in
production with real users and usage scenarios. Canary deployment is one of the best methods
to compare different versions of services side-by-side1. From a cost perspective, the canary
version is cheaper than the blue-green deployment because it does not require two production
environments2. The DevOps team can quickly and safely revert to a previous version of the
application in a Canary release.
Canary releases can te...
Review
Review
