AWS Summit Singapore Webinar Edition | More Containers, Less Operations & Migrate & Modernize Legacy Microsoft Applications with Containers in Thai

© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Kitisak Sriprasert
Solutions Architect, Amazon Web Services
นักสร ้างสมัยใหม่ (Level 300)
เพิ1มคอนเทนเนอร์ ลดปฏิบัติการ

Let’s Talk About Microservices

What are Microservices?
Microservices are an architectural and organizational
approach to software development in which software is
composed of small, independent services that
communicate over well-defined APIs. These services are
owned by small, self-contained teams.
Whitepaper: http://bit.ly/2A0qGdt - Running Containerized Microservices on AWS

Monolithic -> Microservices
webserver
.package
Order UI
Order service
Inventory
service
Shipping
service
Order UI
Inventory
service
Order
service
Shipping
service

Tenets of Microservices Architectures
Do one
thing wellIndependent
Decentralized
Black box
Polyglot
You build it, you run it

Benefits of Microservices Architecture
Agility
Flexible
scaling
Easy
deployment
Technology
freedom
Reusable code Resilience

Any app, any language
Containers Are a Perfect Fit!
Image is the version
Test and deploy same artifact
Stateless servers decrease change risk
Self-contained services
CI/CD pipelines
CONTAINER ENGINE
Simple to model services

Run containerized Docker applications in production
AMAZON ECS

Production Workloads on AWS
AWS VPC
networking mode
Advanced task
placement
Deep integration
with AWS platform
ECS CLI…{ }
Global footprint
Powerful scheduling
engines
Auto scaling
CloudWatch metrics
Load balancers
Linux & Windows

Amazon ECS
EC2 INSTANCES
ECS
AGENT
TASK
CONTAINER
TASK
CONTAINER
ECS
AGENT
TASK
CONTAINER
TASK
CONTAINER AGENT COMMUNICATION
SERVICE
Amazon
ECS
API
CLUSTER MANAGEMENT
ENGINE
KEY/VALUE STORE
ECS
AGENT
TASK
CONTAINER
TASK
CONTAINER
INTERNET LOAD
BALANCER
LOAD
BALANCER

63%
of Kubernetes workload run on
Amazon Web Services today
- CNCF 2017 Survey
https://www.cncf.io/blog/2017/06/28/survey-shows-kubernetes-leading-orchestration-platform/
https://www.cncf.io/blog/2017/12/06/cloud-native-technologies-scaling-production-applications/

E L A S T I C C O N TA I N E R S E R V I C E F O R K U B E R N E T E S
(EKS)

mycluster.eks.amazonaws.com
Availability
Zone 1
Availability
Zone 2
Availability
Zone 3
kubectl

Run containers without managing servers or clusters
AWS FARGATE

AWS Fargate
No instances
to manage
Task
native API
Resource-
based pricing
Simple, easy to use,
powerful, and new
consumption model
=

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

AMAZON CONTAINER SERVICES
Choose your orchestration tool1
Choose your launch type2
ECS EKS
EC2 Fargate EC2 Fargate

● >400 services
currently deployed
● >80 container
instances
● >50,000 deploys
● 6 clusters
● 2 regions
Building a
platform on
Amazon ECS

More Containers, More Operations?

More Containers, More OperationsLESS

Continuous Deployment
AWS
CodeCommit AWS
CodePipeline
AWS
CodeBuild
Amazon ECR
Amazon ECS
AWS
CloudFormation
1. Commit Code
2. Trigger
Pipeline
5.UpdateStack
6. Update Service
4. Push Image
3.BuildArtifact

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

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

Coordinate Microservices with
Visual Workflows

Step Functions and Containers
Container workflows
Video transcoding

Find endpoints,
then connect
Functional calls
Application communication is evolving
Known endpoints, APIs

Developers need to connect micro services
Build apps
invoking other
services by name
Ensure that service
name resolves to
correct IP/port
DEV OPS

“Where is Service X?”
Friendly name -> IP + port
E.g., app: {10.0.4.5:8080, 10.0.4.6:8080 }
What is Service Discovery?
Service registry is a database populated with
information on how to dispatch requests to
microservice instances.

Why is it non trivial?
Dynamic by design:
Number of containers & instances
Auto assigned IP addresses & ports
Placement, scheduling, scaling
Deployments and upgrades
Health and connectivity

SERVICE A
INSTANCE 1
SERVICE B
INSTANCE 1
CLIENT
How to contact you?
What’s your IP+Port?
How to contact you?
What’s your IP+Port?

SERVICE A
INSTANCE 1
SERVICE B
INSTANCE 1
CLIENT
Which one is available?
SERVICE A
INSTANCE 2
SERVICE B
INSTANCE 1
Which one is available?

SERVICE A
INSTANCE 1
CLIENT
SERVICE A
INSTANCE 2
SERVICE B
INSTANCE 1
SERVICE B
INSTANCE 2
Service removed!

SERVICE A
INSTANCE 1
SERVICE B
INSTANCE 1
CLIENT
SERVICE A
INSTANCE 2
SERVICE B
INSTANCE 2
NEW DEPLOYMENT!
SERVICE C
INSTANCE 1
SERVICE C
INSTANCE 2

Current patterns require install, setup and management
Load Balancers Key-value store Service Mesh
Service
registry

Decision Criteria
Service Registry
Discovery Mechanism
Registration Mechanism
Self-registration
Server-side Discovery
Third-party Registration
Client-side Discovery

Can We Make It Simpler?
Predictable
Names
for services
Auto updated
with latest,
healthy IP, port
Managed: No
overhead of
installation or
monitoring
High availability,
high scale
Extensible:
Flexible
boundaries for
auto discovery

Introducing Service Discovery for
Amazon ECS

You build apps where
services are invoked by
name & name resolves
to IP/port dynamically
You turn on service
discovery during
deployment —
service creation
DEV OPS

Service Discovery Components
Service
CNAME: A / SRV record
Namespace

Route 53 provides Service Registry
Route 53 provides APIs to create
• Namespace
• CNAME per service autoname
• A records per task IP
• SRV records per task IP + portService
CNAME: A / SRV record
Namespace

ECS schedules & places service endpoints
ECS Scheduler updates on:
• Service scaling
• Task registrations
• Task de-registrations
• Task health
• Scheduling / Placement changes
• ECS instance changes
ECS maintains latest state of the
dynamic environment in Service
Registry
Cluster: myapp
app
IP
web
IP
app
IP
web
IP
AZ 1 AZ 2

ECS updates service endpoints in Route 53
Cluster: myapp
AZ 1 AZ 2
app
10.0.6.5:8080
web
10.0.8.6:8080
app
10.0.4.5:8080
web
10.0.3.6:8080
Namespace: myapp.local
Service
web.myapp.local CNAME
10.0.4.5:8080
10.0.3.6:8080
Service
app.myapp.local CNAME
10.0.6.5:8080
10.0.8.6:8080

Services connect to latest endpoints via DNS
Service
web.myapp.local CNAME
10.0.4.5:8080
10.0.3.6:8080
app
>dig web.myapp.local
> 10.0.4.5:8080
>
app web
web
Cluster: myapp DNS Server:
AZ 1 AZ 2

Benefits of this approach
Cluster: myapp
AZ 1 AZ 2
Service
Namespace
Managed
Just turn on
Highly available
Tied to Route 53
availability, scale
Extensible
Public APIs that can be
used across AWS
Works across clusters,
accounts, AZs
Works across AWS services

Enables these use cases
1
Blue green deployments
• myapp.staging.local
• myapp.prod.local
• Private IP
• abstract cluster details
2
Internal micro services
• web.myapp.local
• Expose Private IP
3
External micro services
• web.myapp.mycompany.com
• Expose public IP or ELB EIP
• network + container health
check
4
Across ECS & EKS
• Service1.myapp.ecs
• Service2.myapp.eks
5
Across ECS &
AWS & onPrem
• Service1.myapp.ecs
• Service2.myapp.ec2
• Service3.myapp.onprem
6
Expose to service mesh
• Service1.myapp.local
• Service2.myapp.local

Kitisak Sriprasert
Solutions Architect, Amazon Web Services
ย ้ายเลย! ย ้ายข ้อมูลไปยัง AWS (ระดับ 200)
ย ้ายและพัฒนาแอปพลิเคชัน Microsoft
เดิมให ้ทันสมัยด ้วยคอนเทนเนอร์

VM
Container
Who is this new kid in town?

Server
Host OS
Hypervisor
Server
Host OS
VM Containers
Guest OS
Lib,bin
App
VM 1
C 1
AppGuest OS
Lib,bin
App
VM 2
C 2
App
C 3
App
C 4
App
C 5
App
C 6
App
Common bin,lib Common bin,lib
OS Image 1 OS Image 2
Docker
Images
Running
Containers
2 Apps
Vs
6 Apps

Why do we care?
https://pixabay.com/en/baby-boy-child-childhood-computer-84626/

Bob

Customers
AWS cloud
Identity Federation
Active
Directory
Microsoft
Technologies
on AWS
AWS Tools for Windows PowerShell
MSFT SCVMM Plug-in
2008 Today
Innovation
CustomerAdoption
WS 2008 & SQL Server 2008
WS 2003
.NET SDK
WS 2008 R2
SQL Server 2008 R2
Visual Studio
Toolkit
EC2 Dedicated Instances
(BYOL)
MSFT SCOM
plug-in release
Amazon RDS adds SQL Server
WS 2012 & SQL Server 2012
EC2 Run Command
EC2 Dedicated Hosts (BYOL)
MSFT SharePoint 2016 (Marketplace)
AWS Directory Service
WS & SQL 2016
EC2 Systems Manager
.NET on Lambda
Buy license included
instances
Bring your own licenses
Licensing

Windows Instance Example
m4.4xlarge -> $1.736/hr (SIN)
m4.xlarge -> $0.434/hr (SIN)
CPU Utilization ~ 15%
Change Instance Type
CPU Utilization
~60%
Still has ~40% head
room
75%
Savings

Bring Your Own License
(BYOL) – Windows Server
Running two m4.4xlarge instances
~2500 USD
On Demand
~1600 USD
3 Year Reservation
36% Savings
~1600 USD
3 Year Reservation
~800 USD
Dedicated Host
Reserved Instance
50% Savings

m4.4xlarge
25% Utilization
m4.large
50%
Utilization
~1200 USD ~800 USD
m4.large
50%
Utilization
m4.large
50%
Utilization
m4.large
50%
Utilization
33% Savings
m4.4xlarge
75% Utilization
How can I isolate?

So far what we found
Reserved instances
Bigger instances
Right sizing
Easy deployment
Easy Patching
Isolation
Increase
Utilization
Savings
Headache Free IT

Slicing & Isolating Resources
12am 1am 2am 3am 4am 5am 6am 7am 8am 9am 10am 11am
Job 1
Job 2
Job 3

Slicing & Isolating Resources
docker run -d --cpu-percent 10 mycompany/myapp c:AppBatch.exe
12am 1am 2am 3am 4am 5am 6am 7am 8am 9am 10am 11am
Job 1
Job 2
Job 3

Docker Images & Layers
Application 1 Application 2
Layer 110GB
Layer 22GB
Layer 350MB
Layer 410MB
Layer 320MB
Layer 45MB
Shared Layers

Patching and Maintenance
My application 1 layer
version 10
version 200
My application 2 layer
ASP.NET:latest
Windows Server:latest

Set of containers
E.g. SQL server, Web sites
instance instance instance instance
Cluster
Constrains
E.g. HR, Finance, Instance Size
Resource Demand
E.g. Memory, CPU
Task

Cluster
Task
Service
How many task?
Deployment
Strategy?
Auto scaling
Strategy?

Amazon ECS Amazon ECS
Example Deployment
Bin Packing Balance Spread

Cluster
Service 1
Service 2
Service 3
Service N

Efficiency | Agility | Automation
I want…

CI/CD Pipeline
Microsoft
Visual Studio
Application Load
Balancer
v 1
v 1
container
container
Microsoft
TFS
Build Agent Amazon
ECR
Amazon ECS
container
container
v 2
v 2
Security Checks
Unit Test

What we learnt 1/3
Containers
CC https://pixabay.com/en/container-port-loading-stacked-3118783/

What we learnt 2/3
Isolation
CC https://pixabay.com/en/horse-barn-the-horses-are-stallion-2649609/

What we learnt 3/3
Automation
https://commons.wikimedia.org/wiki/File:KUKA_Industrial_Robots_IR.jpg

AWS Summit Singapore Webinar Edition | More Containers, Less Operations & Migrate & Modernize Legacy Microsoft Applications with Containers in Thai

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Ähnlich wie AWS Summit Singapore Webinar Edition | More Containers, Less Operations & Migrate & Modernize Legacy Microsoft Applications with Containers in Thai

Ähnlich wie AWS Summit Singapore Webinar Edition | More Containers, Less Operations & Migrate & Modernize Legacy Microsoft Applications with Containers in Thai (20)

Mehr von Amazon Web Services

Mehr von Amazon Web Services (20)

AWS Summit Singapore Webinar Edition | More Containers, Less Operations & Migrate & Modernize Legacy Microsoft Applications with Containers in Thai