#+HashtagPLUS
In

Menu

Post image 1
Post image 2
Post image 3
Post image 4
Post image 5
Post image 6
Post image 7
Post image 8
Post image 9
Post image 10
Post image 11
Post image 12
Post image 13
Post image 14
Post image 15
Post image 16
Post image 17
Post image 18
Post image 19
Post image 20
Post image 21
Post image 22
Post image 23
Post image 24
Post image 25
Post image 26
Post image 27
Post image 28
Post image 29
Post image 30
Post image 31
Post image 32
Post image 33
Post image 34
Post image 35
1 / 35
0

Modern Deployment Strategies with AWS: Blue/Green and Canary with CodeDeploy

DEV Community·Breindel Medina·20 days ago
#ELWVOIfV
#aws#bluegreen#canary#codedeploy#version#deployment
Reading 0:00
15s threshold

When deploying applications to production, the method you use to replace the old code with the new code dictates your risk level. Historically, deployments meant overwriting the live server. Today, modern architectures use load balancers to shift traffic dynamically, drastically reducing the blast radius of a bad release. Here is an in-depth look at how these deployment strategies work, complete with architectural flows, followed by a manual, CLI-driven hands-on guide to deploying a FastAPI container from Amazon ECR to ECS using AWS CodeDeploy. The Danger of "In-Place" Deployments Deploying without traffic shifting is known as an In-Place Deployment . In practice, this means your server stops serving the current version (Version 1) and replaces it with the new version (Version 2) on the same machine or instance. There is no buffer, no parallel environment, just a direct swap. The Risk: During the replacement, your server is either down or running in a partially updated state.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Create free accountLog in
Read More