我們常碰到儘管容器適合用來運作微服務，但在透過微服務架構運作及管理大規模應用時卻十分艱難的情況，並且通常還需要運用複雜的容器管理基礎架構。大規模量產應用微服務究竟需要哪些要素？在本專題演講中，我們將探討微服務背後的根據和概念，以及了解容器如何簡化建構微服務型應用，另外也將詳細解說客戶用來運作其微服務平台的模式範例。此外，我們也將深入探討運作微服務的特定挑戰，如負載平衡、服務探索和密碼管理，並將說明如何透過 Amazon EC2 Container Service (ECS) 的輔助解決這類挑戰。最後會示範如何使用 Amazon ECS 輕鬆地部署複雜的微服務應用。

1. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Pahud Hsieh(謝洪恩), Solutions Architect
June 7, 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. iCook 愛料理
Leading recipe sharing social network
- 5M+ MAU
- 4M+ app downloads worldwide
- 10k+ recipes / dishes uploaded monthly

10. Agile development for iCook 愛料理
With limited resource, we want to achieve:
1. Use hosted services as mush as possible
2. Easy to install cluster and manage
3. Continuous integration & deployment

11. Why ECS over X?

12. Three major advantages
AWS integration
- Persistent data
- Auto scaling
- Load balancing
Lightweight agent
- Just an image
- Open source
Great SDKs
- Same AWS SDKs
- Easy auth
- Good docs

13. Start using ECS today!
Some time saving tips:
1. Use ECS optimized images
2. Plan auto scaling and load balancing from beginning
3. Learn ECS APIs from SDK

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 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

17. 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

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: Affinity and Anti-Affinity

19. Running a Service

20. 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

21. 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

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

23. 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/

24. Reference Architectures

25. 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

26. 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

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

28. 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

29. Blue-Green Deployments
TaskTask
Route 53
record set
with
weighted
routing
policy
0%
100%

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. 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

32. 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

33. Build Learn
Try It out
Deploy

34. Thank You