Aws microservice keynote

1. Microservice Architecture
on Amazon Web Services
Alex Sinner
Solutions Architect,
Amazon Web Services
@alexsinner

2. Why Microservices?

3. http://en.wikipedia.org/wiki/Multitier_architecture

4. As a Project scales Complexity arises

5. How to design
smaller services?

6. Monolithic application vs Microservices
http://martinfowler.com/articles/microservices.html

8. Business Domain!
+
Loosely Coupled
+
Bounded Context

9. Microservices
Independent Deployment!

10. Microservices
Choose the Right Tools!

11. Microservices
Adopt New Technologies!

12. Microservices
Culture of Automation!

13. How small is small?

14. “something that could be
rewritten in two weeks”

15. Two Pizza Teams!

16. Architecture
DevOps

17. Containers & event-driven computing

18. Virtual Machine! Container!

19. Docker on AWS!
Amazon!
Linux!
!
!
A supported and
maintained Linux
image provided by
Amazon Web Services!
!
Amazon EC2
Container
Service!
!
Highly scalable, high
performance container
management service!
!
!
AWS!
Elastic
Beanstalk!
!
For deploying and
scaling web
applications and
services!
!

20. Amazon EC2 Container Service!
Key Components
Clusters!
Container Instances!
Tasks
Task Definitions
Task Scheduler
Regional
Resource pool
Grouping of Container Instances
Start empty, dynamically scalable

21. Amazon EC2 Container Service!
Key Components
Clusters
Container Instances!
Tasks
Task Definitions
Task Scheduler
Amazon EC2 instances
Docker daemon
Amazon ECS agent

22. https://github.com/aws/amazon-ecs-agent

23. Amazon EC2 Container Service!
Key Components
Container Instances
Clusters
Tasks
Task Definitions
Task Scheduler
Unit of work
Grouping of related Containers
Run on Container Instances

24. Amazon EC2 Container Service!
Key Components
Container Instances
Clusters
Tasks
Task Definitions!
Task Scheduler!
[
{
"image": "mysql",
"name": "db",
"cpu": 10,
"memory": 500,
…

25. Tasks are defined via Task Definitions
[!
{!
"image": "tutum/wordpress-stackable",!
"name": "wordpress",!
"cpu": 10,!
"memory": 500,!
"essential": true,!
"links": [!
"db"!
],!
"entryPoint": [!
"/bin/sh",!
"-c"!
],!
"environment": [!
…!
],!
"portMappings": [!
{!
"containerPort": 80,!
"hostPort": 80!
}!
]!
},!
!
!
{!
"image": "mysql",!
"name": "db",!
"cpu": 10,!
"memory": 500,!
"essential": true,!
"entryPoint": [!
"/entrypoint.sh"!
],!
"environment": [!
{!
"name": "MYSQL_ROOT_PASSWORD",!
"value": "pass"!
}!
],!
"portMappings": []!
}!
]!

26. [!
{!
"image": "tutum/wordpress-stackable",!
"name": "wordpress",!
"cpu": 10,!
"memory": 500,!
"essential": true,!
"links": [!
"db"!
],!
"entryPoint": [!
"/bin/sh",!
"-c"!
],!
"environment": [!
…!
],!
"portMappings": [!
{!
"containerPort": 80,!
"hostPort": 80!
}!
]!
},!
]!
!
{!
"image": "mysql",!
"name": "db",!
"cpu": 10,!
"memory": 500,!
"essential": true,!
"entryPoint": [!
"/entrypoint.sh"!
],!
"environment": [!
{!
"name": "MYSQL_ROOT_PASSWORD",!
"value": "pass"!
}!
],!
"portMappings": []!
}!
]!
From Docker Hub
10 CPU Units (1024 is full CPU),
500 Megabytes of Memory
Environment Variables
No external ports exposed
Tasks are defined via Task Definitions

27. [!
{!
"image": "tutum/wordpress-stackable",!
"name": "wordpress",!
"cpu": 10,!
"memory": 500,!
"essential": true,!
"links": [!
"db"!
],!
"entryPoint": [!
"/bin/sh",!
"-c"!
],!
"environment": [!
…!
],!
"portMappings": [!
{!
"containerPort": 80,!
"hostPort": 80!
}!
]!
},!
!
[!
{!
"image": "mysql",!
"name": "db",!
"cpu": 10,!
"memory": 500,!
"essential": true,!
"entryPoint": [!
"/entrypoint.sh"!
],!
"environment": [!
{!
"name": "MYSQL_ROOT_PASSWORD",!
"value": "pass"!
}!
],!
"portMappings": []!
}!
]!
Essential to our Task
Docker link to mysql container
Expose port 80 in container
to port 80 on host
Tasks are defined via Task Definitions

28. Amazon EC2 Container Service!
Key Components
Container Instances
Clusters
Tasks
Task Definitions
Task Scheduler
Long-running services
RunTask for batch jobs
Integrate with 3rd party schedulers

29. AWS Lambda!
!
Zero Admin!
Event-driven
Compute Platform!

30. AWS Lambda!
!
Focus on business logic,!
not infrastructure!
Customer uploads code,
AWS Lambda handles:
Capacity
Scaling
Deployment
Fault tolerance
Monitoring
Logging
. . .

31. AWS Lambda
Automatic scaling
Customers pay only
for what they use,
no over/under provisioning

32. AWS Lambda
Fine-grained pricing
Price compute time by 100ms,
even short jobs make sense
Low request charge
No hourly, daily, or monthly minimums
Free tier

33. Events come in many different shapes & sizes
S3 event
notifications
DynamoDB
Streams
Kinesis events Custom
events

34. AWS Lambda
Asynchronous Invocation Synchronous Invocation
AWS Lambda
Event RequestResponse
Response
Response
CloudWatch
Logs
vs

35. Mobile & IoT
AWS Lambda Backends!

36. Amazon EC2
Containers
AWS Lambda
On-Premises
Weeks Minutes Seconds Milliseconds
Infrastructure Scaling

37. Amazon EC2
Containers
AWS Lambda
On-Premises
Low High Higher Highest
Infrastructure Utilization

38. Thank You!
@alexsinner