Deep Dive on Microservices and Docker

1. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Tom Fuller, Senior Solutions Architect
8/17/2017
Deep Dive on Microservices
and Docker

2. What to Expect from the Session
• Microservices Architecture
• Amazon ECS
• Task Placement
• The Twelve-Factor App with Amazon ECS

3. Microservices Architecture

4. What are microservices?
“A software architecture style in which complex
applications are composed of small, independent
processes communicating with each other using
language-agnostic APIs. These services are small, highly
decoupled and focus on doing a small task, facilitating a
modular approach to system-building.” - Wikipedia
https://en.wikipedia.org/wiki/Microservices

5. Monolithic vs. Microservices
webserver
.package
Order UI
Order Service
Inventory
Service
Shipping
Service
OrderUI
Inventory
Service
Order
Service
Shipping
Service

6. Characteristics of Microservice Architectures
Do one
thing wellIndependent
Decentralized
Black box
Polyglot
You build it, you run it

7. Why Amazon ECS
• Fully managed elastic service – You don’t
need to run anything, and the service
scales as your microservices architecture
grows
• Shared state optimistic scheduling
• Integration with CloudWatch service for
monitoring and logging
• Integration with Code* services for
continuous integration and delivery (CI/CD)

8. Deploying Containers on ECS – Choose a Scheduler
Batch Jobs
ECS task scheduler
Run tasks once
Batch jobs
RunTask (random)
StartTask (placed)
Long-Running Apps
ECS service scheduler
Health management
Scale-up and scale-down
AZ aware
Grouped containers

9. Problem:
• A large number of smart phone devices and IoT
devices as of the launch of new flagship
smartphone model launch.
• Integration with existing SmartThings service
• Global development team in 4 locations had to
develop more than 60 functional modules.
Solution:
• Micro-Service Architecture on AWS
• AWS EC2 Container Service, AWS Lambda,
Amazon Aurora, Amazon DynamoDB
Business Benefits:
• “Expect a rich IoT experience with Samsung
Connect built on Amazon's robust cloud” – VP
Subaek Jang
Samsung Connect Service supports a number of smart
phone devices and IoT devices as of the launch of new
flagship smartphone model launches. AWS service such
as AWS EC2 Container Service, AWS Lambda, Amazon
Aurora and Amazon DynamoDB, Samsung could
successfully develop Samsung Connect application with
more than 60 functional modules by 4 global development
teams in Micro-Service Architecture.
• AWS Seoul Summit Keynote -
https://youtu.be/061bsq0jVYU?t=1h16m
Customer Case : Samsung Electronics – Samsung Connect
Samsung
Connect

10. IoT Connected
Devices
Event Pipeline
EC2
S3
Galaxy Devices Microservice
Microservice
Microservice
IoT Protocol
Endpoint
ELB/ALB
DynamoDB &
Aurora
Manufacturers
Developers
KMS
CloudHSM
Lambda/
API GW
3rd Party Cloud
Admin
CloudWatch
Scale-in/out
Policy
…..
Microservices Architecture of Samsung Connect
Microservice

11. WatchBot
ECS Cluster
SQS
Watcher
Container
Running
Tasks
14
Data Processing
Services
3500
Peak Container
Instances
500 million
Compute Hours
Used in 2016

12. Instacart’s PaaS
Coordinated through RDS database
Same tooling local & cloud
Jobs take desired state from DB, and turn
it into cloud reality

13. • Media Encoding Experimentation
• Digital Watermarking
Netflix

14. Amazon ECS: Under the Hood
ALB ALB
AZ 1 AZ 2
user / scheduler
Scheduler
Cluster State Service
Placement Engine
Event Stream

15. Task Placement Examples

16. g2.2xlarge t2.small g2.2xlarge g2.2xlarge
Placement: Targeting Instance Type

17. g2.2xlarge t2.small t2.micro t2.medium
t2.medium t2.small g2.2xlarge
t2.small
t2.small t2.medium
us-east-1aus-east-1d
Placement: Targeting Instance Type & Zone

18. g2.2xlarge t2.small t2.micro t2.medium
t2.medium t2.small g2.2xlarge t2.small
us-east-1aus-east-1d
g2.2xlarge t2.medium
t2.micro t2.small
us-east-1c
Placement: Availability Zone Spread

19. g2.2xlarge t2.small t2.micro t2.medium
t2.medium t2.small g2.2xlarge t2.small
us-east-1aus-east-1d
g2.2xlarge t2.medium
t2.micro t2.small
us-east-1c
Placement: Spread across Zone and Binpack

20. g2.2xlarge t2.small t2.micro t2.medium
t2.medium t2.small g2.2xlarge t2.small
us-east-1aus-east-1d
g2.2xlarge t2.medium
t2.micro t2.small
us-east-1c
Placement: Affinity and Anti-Affinity

21. Running a Service

22. t2.medium t2.small t2.small
us-east-1aus-east-1d
t2.medium t2.micro t2.small
us-east-1c
Placement: Multiple Services on a Cluster

23. t2.medium g2.2xlarge t2.micro t2.small
t2.small t2.small g2.2xlarge t2.small
t2.small t2.small
g2.2xlarge t2.small
Placement: Services – Distinct Instances

24. The Twelve-Factor App with
Amazon ECS
Reference Architectures

25. The Twelve-Factor App
1. Codebase
2. Dependencies
3. Config
4. Backing Services
5. Build, Release Run
6. Processes
7. Port Binding
8. Concurrency
9. Disposability
10. Dev/Prod parity
11. Logs
12. Admin Processes
https://12factor.net/

26. Reference Architectures

27. Example Microservice Architecture on ECS
Amazon
ECR
Amazon
RDS
Application Load
Balancer
ECS Cluster
ECS Cluster
IAM
Amazon API
Gateway*
Amazon
Route 53
Amazon CloudWatch

28. Automatic Service Scaling
Publish metrics
Auto Scaling ECS service
Availability
Zone A
Availability
Zone B
TASK A
Add/Remove ECS
tasks
TASK C
TASK BScaling Policies
Amazon
CloudWatch
Amazon ECS
Application
Load Balancer

29. IAM Roles For Tasks
ECS Cluster
EC2 Instance EC2 Instance
TASK A
TASK B
TASK B
Amazon
DynamoDB
Amazon
S3

30. Secrets Management
•prod.app1.db-pass
•general.license-code
•prod.app2.user-name
ECS Cluster
EC2 Instance EC2 Instance
TASK A
TASK B
TASK B
EC2 System Manager –
Parameter Store

31. Continuous Deployment
AWS
CodeCommit AWS
CodePipeline
AWS
CodeBuild
Amazon
ECR
Amazon
ECS
instance
Spot
Instance
AWS
CloudFormati
on
1. Commit
Code
2. Trigger
Pipeline
3.Build
Artifact
5.Update
Stack
6. Update Service
4. Push Image

32. Blue-Green Deployments ( DNS based)
TaskTask
Route 53
record set
with
weighted
routing
policy
0%
100%

33. Blue-Green Deployments ( Target Group Switch)
TaskTask
Target
group 1
Target
group 2
Target
group 2
Target
group 1
Switch Target
Groups
myproduct.com

34. Canary Deployment
Update traffic weights
10 20 50

35. Task Rebalancing
Update service

36. Task Rebalancing with Placement Strategy
Update service
Schedule tasks
{
“cluster” : “ecs-demo”,
“serviceName”: “my-service”,
“taskDefinition” : “my-app”,
“desiredCount” : 5,
"placementConstraints": [
{
"type": "distinctInstance"
}
],
"placementStrategy": [
{
"type": "random”
}
]

37. Autoscaling life cycle hooks
http://docs.aws.amazon.com/autoscaling/latest/userguide
/lifecycle-hooks.html

38. Service Discovery with Route 53 and Application
Load Balancers
Application Load
Balancer
i-aaa i-bbb i-ccc
i-aaa i-bbb i-ccc
oAuth Target Group
8080 8081
Portal Target Group
Weather Target Group
8000 8001 8002
8080
Amazon
Route 53
ECS Cluster
mydomain.com
mydomain.com mydomain.com/weather
mydomain.com/auth

39. Event Stream

40. Consuming Events for Service Discovery
app1-tst à 10.1.0.11
db1-tst à 10.1.0.14
app2 à 10.1.0.16
db2 à 10.1.0.18
my-app à 10.1.0.20
websrv1à 10.1.0.1
websrv2à 10.1.0.2
websrv3à 10.1.0.4
app-dev1à 10.1.0.9
app-dev2à 10.1.0.5
app-dev3à 10.1.0.8
db-devà 10.1.0.19

41. Governance: AWS Service Catalog
Organizations Developers
Control
Standardization
Governance
Agility
Self-service
Time to market

42. Creates portfolio
Adds constraints and grant access
1
4
5
Administrator
Portfolio
Users
Browse Products
6Launch Products
Creates
product3Authors template2
Product
X
Product
Y
Product
Z
7
Deploys
stacks
Notifications
Notifications
8
8
Governance: AWS Service Catalog

43. Build Learn
Try It out
Deploy

44. https://s3-us-west-2.amazonaws.com/apn-
bootcamps/microservice-ecs-2017/lab-guide.html

45. Thank You

46. Introducing Blox

47. What is Blox?
Choice
Control
Developer Experience

48. Building with Blox
scheduler cluster state service

49. Set Up Blox Locally
Step 1: git clone https://github.com/blox/blox.git
Step 3: docker-compose up -d
Step 4: start using Blox locally
Step 2: deploy CloudFormation template to configure ECS event stream and SQS queue

50. Swagger Spec: Cluster State Service

51. Swagger Spec: Daemon Scheduler

52. Daemon Scheduler

53. t2.small t2.small t2.small
Blox: Daemon Scheduler
t2.small t2.small t2.small
scheduler cluster state service
t2.small t2.small t2.small

54. Step 1: Create an Environment

55. Step 2: Create a Deployment

56. Step 3: Add Container Instances

57. Step 4: Monitoring and Scaling a Cluster

58. Contributing to Blox
• Blox is licensed under Apache 2.0
• Open an issue or pull request
• Watch our roadmap on GitHub
• Check out our Gitter channel

59. The Blox Vision