Breaking the Monolith Using AWS Container Services

© 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
P U B L I C S E C T O R
S U M M I T
Breakingthe Monolith - Best Practices to
RunYourContainersin theCloud
Sébastien Stormacq
Technical Evangelist, AWS
@sebsto

© 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.P U B L I C S E C T O R
S U M M I T

The12 factorapplication
I. Codebase
One codebase w/ revision control, many deploys
II. Dependencies
Explicitly declare and isolate dependencies
III. Config
Store config in the environment
IV. Backing services
Treat backing services as attached resources
V. Build, release, run
Strictly separate build and run stages
VI. Processes
Execute the app as one or more stateless processes
VII. Port binding
Export services via port binding
VIII. Concurrency
Scale out via the process model
IX. Disposability
Fast startup and graceful shutdown
X. Dev/prod parity
Keep environments as similar as possible
XI. Logs
Treat logs as event streams
XII. Admin processes
Run admin/management tasks as one-off processes

Youknowwhat’sgreatfora12 factorapp?

RUNNINGASINGLECONTAINER

EC2 Instance
TaskTask
Task Task
EC2 Instance
TaskTask
Task Task
EC2 Instance
TaskTask
Task Task
EC2 Instance
TaskTask
Task Task
EC2 Instance
TaskTask
Task Task
RUNNINGCONTAINERS

RUNNINGCONTAINERSATSCALEWITHECS
Availability Zone #1 Availability Zone #2 Availability Zone #3
Scheduling and Orchestration
Cluster Manager Placement Engine

ECS
AMI
Docker
agent
ECS
agent
ECSTaskECSTask
ECSTaskECSTask
EC2 Instance

ECS
AMI
Docker
agent
ECS
agent
EC2 Instance
ECS
AMI
Docker
agent
ECS
agent
EC2 Instance
ECS
AMI
Docker
agent
ECS
agent
EC2 Instance
Scheduling and Orchestration
Cluster Manager Placement Engine

“Just launch 10 copies of
my container distributed
across three availability
zones and connect them to
this load balancer”
X 10

S U M M I T
One codebase tracked in revision control, many deploys

DeployedVersionCode Version Control

Staging / QA
Production
Dev #1
Dev #2

S U M M I T
Explicitly declare and isolate dependencies

Dependencies
Binaries
Code
Application
Bundle

DependencyDeclaration:Node.js
package.json
npm install
# - or -
yarn install

DependencyDeclaration:Python
requirements.txt
pip install

Dependencies
Dependencies
Binaries
Code

DependencyDeclaration& Isolation: Docker
Dockerfile
docker build

S U M M I T
Store config in the environment

Development
Configuration
Production
Configuration
Development
Production

Development
Production
Same container deployed to both environments.
Configuration is part of the environment on the host.

Atruntimethecontainergetsconfigfromthe
environment.

Application code pulls from the environment
Environment is customized when docker runs a container

AWSSecretsManager&TaskDefinitions
"containerDefinitions": [
{ "secrets": [
{ "name": "environment_variable_name",
"valueFrom": ”arn_of_your_secret"
}
]
}
]

S U M M I T
Treat backing services as attached resources

PostgreSQLapp1
Host
app2 3rd party service
Treat local services just like remote third party ones

PostgreSQLapp1
app2
Load balancer
Use CNAMES for maximum flexibility and
easy reconfiguration
postgres.mycompany.com
app2.mycompany.com

Easily create and maintain custom maps of your applications
Before
Version 2
After
Version 2

S U M M I T
Strictly separate build and run stages

Build
Dependencies
Binaries
Code

Release
Config ReleaseBuild Artifact
+ =
Tagged image stored in ECR

Amazon ElasticContainerService
Config

Run
Task Definition Release v1
Task Definition Release v2

CodeDeploy-ECSappspec
version: 1.0
Resources:
- TargetService:
Type: AWS::ECS::Service
Properties:
- TaskDefinition: "my_task_definition:8"
LoadBalancerInfos:
- ContainerName: "SampleApp"
ContainerPort: 80
Hooks:
- BeforeInstall: "LambdaFunctionToExecuteAnythingBeforeNewRevisionInstalltion"
- AfterInstall: "LambdaFunctionToExecuteAnythingAfterNewRevisionInstallation"
- AfterAllowTestTraffic: "LambdaFunctionToValidateAfterTestTrafficShift"
- BeforeAllowTraffic: "LambdaFunctionToValidateBeforeTrafficShift"
- AfterAllowTraffic: "LambdaFunctionToValidateAfterTrafficShift"

CodeDeploy-ECSblue-greendeployment
100%
Prod
traffic

Target group
2
100%
Prod
traffic
Test traffic listener
(port 9000)

Green tasks:
v2 code
100%
Prod
traffic
Provision green tasks

100%
Test
traffic
100%
Prod
traffic
Run hook against test endpoint before green tasks receive prod traffic

100%
Prod
traffic
Flip traffic to green tasks, rollback in case of alarm
0% Prod
traffic

100%
Prod
traffic
Drain blue tasks

Containerimagetaggingfordeployments
• Docker tags are resolved when each container starts, not just during
deployments
• Deploying “latest” or “prod” can result in untested code in production
after a scale-out event
• Use unique “immutable” tags for deployments

Build pushes new “latest” image
Image: sha256@22222... (“latest”)

Service scales up, launching new tasks
Image: sha256@22222... (“latest”)

Deploy using immutable tags
{
"name": "sample-app",
"image": "amazon/amazon-ecs-
sample@sha256:3e39d933b1d948c92309bb583b5a1f3d28f0119e1551ca1fe538ba414a41af48d"
}
{
"name": "sample-app",
"image": "amazon/amazon-ecs-sample:build-b2085490-359f-4eaf-8970-6d1e26c354f0"
}
SHA256 Digest
Build ID

Compute immutable tags during build
SHA256 Digest
export IMAGE_URI=`docker inspect --format='{{index .RepoDigests 0}}'
my_image:$IMAGE_TAG
Example Result:
amazon/amazon-ecs-sample@sha256:3e39d933b...
Build ID
export IMAGE_TAG=build-`echo $CODEBUILD_BUILD_ID | awk –F":" ‘{print $2}'`
Example Result:
build-b2085490-359f-4eaf-8970-6d1e26c354f0

Build pushes new image tagged with new build ID
Image: sha256@22222... (“build-22222”)

Service scales up, launching new tasks
Image: sha256@22222... (“build-22222”)

Image: “build-22222” tag
Deployment updates service’s task definition, replacing tasks
Image: sha256@22222... (“build-22222”)

S U M M I T
Execute the app as one or more stateless processes

Stateful container stores state in local disk or local memory.
Workload ends up tied to a specific host that has state data.
eu-west-1b
Container 1
Disk
eu-west-1ceu-west-1a

Statefuldata
Use services:
• Amazon RDS
• Amazon DynamoDB
• Amazon ElasticCache
• Amazon ElasticSearch
• Amazon S3
• ……

S U M M I T
Export services via port binding

Port 32456
Port 32457
Port 32458

Port 32768
Port 33487
Port 32192
Port 32794
Port 32781
Match: /api/users*
Match: /api/auth*

S U M M I T
Keep development, staging, and production as similar as possible

Dev #1
Dev #2
Staging / QA
Production

Staging / QA
Production
Dev #1
Dev #2
Local Application Remote

Model containerenvironmentswithAWS
Cloud DevelopmentKit(CDK)
Developer
Preview
• Open source framework to define cloud
infrastructure in TypeScript, Java, C#, …
• Provides library of higher-level resource types
(“construct” classes) that have AWS best practices
built in by default, packaged as npm modules
• Provisions resources with CloudFormation
• Supports all CloudFormation resource types
AWS
CDK
https://awslabs.github.io/aws-cdk

CDKtemplate
import ec2 = require('@aws-cdk/aws-ec2');
import ecs = require('@aws-cdk/aws-ecs');
import cdk = require('@aws-cdk/cdk');
class BonjourFargate extends cdk.Stack {
constructor(parent: cdk.App, name: string, props?: cdk.StackProps) {
super(parent, name, props);
const vpc = new ec2.VpcNetwork(this, 'MyVpc', { maxAZs: 2 });
const cluster = new ecs.Cluster(this, 'Cluster', { vpc });
new ecs.LoadBalancedFargateService(
this, "FargateService", {
cluster,
image: ecs.DockerHub.image("amazon/amazon-ecs-sample"),
});
}
}
const app = new cdk.App();
new BonjourFargate(app, 'Bonjour');
app.run();

import ec2 = require('@aws-cdk/aws-ec2');
import ecs = require('@aws-cdk/aws-ecs');
import cdk = require('@aws-cdk/cdk');
class BonjourFargate extends cdk.Stack {
constructor(parent: cdk.App, name: string, props?: cdk.StackProps) {
super(parent, name, props);
const vpc = new ec2.VpcNetwork(this, 'MyVpc', { maxAZs: 2 });
const cluster = new ecs.Cluster(this, 'Cluster', { vpc });
new ecs.LoadBalancedFargateService(
this, "FargateService", {
cluster,
image: ecs.DockerHub.image("amazon/amazon-ecs-sample"),
});
}
}
const app = new cdk.App();
new BonjourFargate(app, 'Bonjour');
app.run();
CDKtemplate

S U M M I T
Treat logs as event streams

Docker connects container’s stdout to a log driver
Containerized code writes to stdout

CLOUDWATCHLOGSCONFIGURATION
{
"containerDefinitions": [
{
"name":“scorekeep-api",
...
"logConfiguration": {
"logDriver": "awslogs",
"options": {
"awslogs-group": "scorekeep",
"awslogs-region": “us-east-1",
"awslogs-stream-prefix": "scorekeep/api"}}
}
]}

CLOUDWATCHLOGS
Logs Tab in the
Task Detail Page
View logs in the ECS or Cloudwatch Console

Thank you!
S U M M I T
Sébastien Stormacq
Technical Evangelist, AWS
@sebsto

Breaking the Monolith Using AWS Container Services

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Ähnlich wie Breaking the Monolith Using AWS Container Services

Ähnlich wie Breaking the Monolith Using AWS Container Services (20)

Mehr von Amazon Web Services

Mehr von Amazon Web Services (20)

Breaking the Monolith Using AWS Container Services

Hinweis der Redaktion