Continuous Deployment with Auto Scaling by Dominic Umbeer

We Help You to ...

•  Plan your app launch

•  Scale your user base

•  Maximize your revenue

Applaunch

User retention &monetization

UseracquisitionApp user

analysis&

targeting

~ 35,000 Requests per Second

Trademob on AWS

~ 120 Instances

10 Auto Scaling Groups

3 - 5 Deployments

per Week

Continuous Deployments

Requests per Minute Number of Instances

700,000

600,000

400,000

200,000

500,000

300,000

100,000

15

14

13

11

10

8

7

5

4

12

9

6

30

00:00 02:00 04:00 06:00 08:00 10:00 12:00 14:00 16:00 18:00 20:00 22:00

Continuous Deployments

Requests per Minute Number of Instances

700,000

600,000

400,000

200,000

500,000

300,000

100,000

15

14

13

11

10

8

7

5

4

12

9

6

30

00:00 02:00 04:00 06:00 08:00 10:00 12:00 14:00 16:00 18:00 20:00 22:00

What Is Important

Stable & Reliable Auto Scaling Process 1

Fast Scaling 2

Rollback 3

Instance Launch

Launch Time

Production Ready

Software Installations

External Dependencies

Deployment Application/Service

Instance Launch

Launch Time

Production Ready

Software Installations

External Dependencies

Deployment Application/Service

Amazon Machine Image (AMI)

Launch Time

Software Installations

External Dependencies

Deployment Application/Service

Amazon Machine Image (AMI)

Launch Time

AMI Creation

Software Installations

External Dependencies

Deployment Application/

Service

ASG – AMI Configuration

Auto Scaling Group

Availability Zone 1 Availability Zone 2

AMI

ASG – AMI Configuration

Auto Scaling Group

Availability Zone 1 Availability Zone 2

AMI

ASG – Instance Replacement

Auto Scaling Group

Availability Zone 1 Availability Zone 2

AMI

ASG – Instance Replacement

Auto Scaling Group

Availability Zone 1 Availability Zone 2

AMI

ASG – Instance Replacement

Auto Scaling Group

Availability Zone 1 Availability Zone 2

AMI

Facts in a Nutshell

Higher Stability of Auto Scaling Groups 1

Faster Instance Launch 2

Release == AMI 3

Rollback 4