Why Zero-downtime deployment pattern in Terraform? - Purpose & Use Cases

The Big Idea

What if you could update your website without anyone noticing a thing?

The Scenario

Imagine you have a popular website that needs an update. You try to update the server manually by stopping it, changing the code, and starting it again. During this time, visitors see errors or can't access the site at all.

The Problem

Manually updating servers causes downtime because the site is offline while changes happen. It's slow, risky, and users get frustrated. If something goes wrong, fixing it takes even longer, making the problem worse.

The Solution

The zero-downtime deployment pattern lets you update your service without stopping it. It uses two versions running side by side, switching traffic smoothly from the old to the new version. This keeps the site live and users happy.

Before vs After

✗ Before

stop server
update code
start server

✓ After

deploy new version
switch traffic to new version
remove old version

What It Enables

You can update your applications anytime without interrupting users or risking downtime.

Real Life Example

A streaming service updates its video player software while millions watch, without any interruption or buffering caused by the update.

Key Takeaways

Manual updates cause downtime and user frustration.

Zero-downtime deployment runs old and new versions together to avoid interruptions.

This pattern keeps services live and reliable during updates.

Practice

1. What is the main goal of a zero-downtime deployment in Terraform?

easy

A. Manually switch traffic after deployment

B. Update applications without stopping them or causing downtime

C. Deploy new versions only during off-hours

D. Stop all running tasks before updating

Solution

1. Step 1: Understand zero-downtime deployment purpose

   Zero-downtime deployment means updating apps without stopping them or causing service interruptions.

2. Step 2: Compare options with this goal

   Only Update applications without stopping them or causing downtime describes updating without stopping or downtime, matching the goal.

3. Final Answer:

   Update applications without stopping them or causing downtime -> Option B

4. Quick Check:

   Zero-downtime = no stopping, no downtime [OK]

Hint: Zero downtime means no stopping or service interruption [OK]

Common Mistakes:

• Thinking deployment must stop all tasks
• Assuming manual traffic switch is required
• Believing updates only happen off-hours

2. Which Terraform setting helps control how many tasks run during an update for zero-downtime?

easy

A. min_healthy_percent

B. max_percent

C. desired_count

D. task_definition

Solution

1. Step 1: Identify settings related to task counts during update

   Terraform uses settings like max_percent and min_healthy_percent to control task numbers during deployment.

2. Step 2: Understand min_healthy_percent role

   min_healthy_percent ensures a minimum percentage of tasks stay healthy and running during updates, preventing downtime.

3. Final Answer:

   min_healthy_percent -> Option A

4. Quick Check:

   min_healthy_percent controls running tasks during update [OK]

Hint: min_healthy_percent keeps tasks running during updates [OK]

Common Mistakes:

• Confusing max_percent with min_healthy_percent
• Using desired_count which sets total tasks, not update behavior
• Selecting task_definition which defines task specs

3. Given this Terraform snippet for ECS service update:

deployment_minimum_healthy_percent = 75
deployment_maximum_percent = 200

What does this configuration ensure during deployment?

medium

A. Exactly 75 tasks run; maximum 200 tasks allowed

B. No new tasks start until all old tasks stop

C. Deployment stops 25% of tasks before starting new ones

D. At least 75% of tasks stay running; up to 200% tasks can run temporarily

Solution

1. Step 1: Interpret deployment_minimum_healthy_percent

   This means at least 75% of current tasks must stay healthy and running during deployment.

2. Step 2: Interpret deployment_maximum_percent

   This allows up to 200% of the desired tasks to run temporarily, enabling new tasks to start before old ones stop.

3. Final Answer:

   At least 75% of tasks stay running; up to 200% tasks can run temporarily -> Option D

4. Quick Check:

   Min healthy 75%, max 200% = safe rolling update [OK]

Hint: Min healthy % keeps tasks running; max % allows extra tasks [OK]

Common Mistakes:

• Thinking percentages mean exact task counts
• Assuming deployment stops tasks before starting new ones
• Confusing min and max percentages

4. You set deployment_minimum_healthy_percent = 100 and deployment_maximum_percent = 100 in Terraform for ECS service. What issue will this cause?

medium

A. Deployment will run twice the desired tasks temporarily

B. Deployment will succeed with zero downtime

C. Deployment will fail because no new tasks can start before old ones stop

D. Deployment will ignore these settings and use defaults

Solution

1. Step 1: Analyze min and max percent both at 100%

   Min healthy 100% means all old tasks must stay running; max 100% means no extra tasks can start.

2. Step 2: Understand deployment impact

   New tasks cannot start until old ones stop, but old ones cannot stop because min healthy is 100%, causing deployment to fail.

3. Final Answer:

   Deployment will fail because no new tasks can start before old ones stop -> Option C

4. Quick Check:

   Min 100% + Max 100% blocks rolling update [OK]

Hint: Min 100% and Max 100% blocks task replacement [OK]

Common Mistakes:

• Assuming deployment will succeed without downtime
• Thinking max 100% allows extra tasks
• Ignoring min healthy effect on stopping old tasks

5. You want to deploy a new version of your app with zero downtime using Terraform ECS service. Your desired task count is 4. Which configuration best supports zero-downtime deployment?

hard

A. deployment_minimum_healthy_percent = 75deployment_maximum_percent = 125

B. deployment_minimum_healthy_percent = 100deployment_maximum_percent = 100

C. deployment_minimum_healthy_percent = 50deployment_maximum_percent = 150

D. deployment_minimum_healthy_percent = 0deployment_maximum_percent = 200

Solution

1. Step 1: Evaluate each option for zero-downtime support

   deployment_minimum_healthy_percent = 50
deployment_maximum_percent = 150 allows only 50% healthy tasks, risking downtime. deployment_minimum_healthy_percent = 100
deployment_maximum_percent = 100 blocks new tasks starting before old stop. deployment_minimum_healthy_percent = 0
deployment_maximum_percent = 200 allows zero healthy tasks, risking downtime. deployment_minimum_healthy_percent = 75
deployment_maximum_percent = 125 keeps 75% healthy and allows 125% max tasks, enabling smooth rolling update.

2. Step 2: Choose best balance for zero-downtime

   deployment_minimum_healthy_percent = 75
deployment_maximum_percent = 125 ensures enough healthy tasks remain while allowing new tasks to start before old stop, supporting zero downtime.

3. Final Answer:

   deployment_minimum_healthy_percent = 75 and deployment_maximum_percent = 125 -> Option A

4. Quick Check:

   Min healthy 75% + max 125% = safe rolling update [OK]

Hint: Min healthy ~75% and max ~125% enable zero downtime [OK]

Common Mistakes:

• Choosing min healthy too low risking downtime
• Choosing min and max both 100% blocking updates
• Allowing zero healthy tasks during deployment