SDLC - Software Development Lifecycle

Question 1

Deployment Strategies - What is Single Target Deployment

Answer 1

Builds are ran on a single target. Has the drawback of limited testing. To be used on legacy or small development services where possible.

Question 2

Deployment Strategies - All-at-OnceDeployment

Answer 2

Similar to single target, but allows for one step deployment to multiple targets. No ability to test and roll back is not always easy.

Question 3

Deployment Strategies - Minimum in-service Deployment

Answer 3

Users set a minimum number of services that must remain operational. The system then tries to deploy the maximum number of upgrades while maintaining the minimum. Deployment happens in multiple stages and allows for health checks and automated testing. This allows generally no downtime.

Question 4

Deployment Strategies - Rolling Deployments.

Answer 4

A specified number of deployment targets are given. So one can specify a number like 1,2,3 servers at a time, and then each of these numbers are done at a time. Overall applicable health isn’t necessarily maintained. Orchestration and health checks are required. May be slower to deploy if there are many targets.

Question 5

Deployment Strategies - Blue/Greed Deployment

Answer 5

Uses a pointer like DNS load balancing to point services to an initial Blue service. Blue is then effectively copied to a full replica Green product and then the changes are made to the new green deployment and then DNS point over to Green.

Question 6

Deployment Strategies - Canary Deployment

Answer 6

Same as Blue/Green but the switch over to green is slowly integrated using both Blue/Green simultaneously and then switching over slow using Route53 Weighted Round Robin.

Question 7

What is CodeDeploy?

Answer 7

A managed deployment service that automates deployment to ECS, On-premise instances and Lambda.

Question 8

How does CodeDeploy know where to deploy software too?

Answer 8

It can use auto-scaling or tags.