Container in cloud with Amazon Web Services

1. AWSome Day 2018
Scalability and cost optimization
with Container Services
AWSome Day - Torino 2018

2. Walter Dal Mut
Solution Architect - AWS Certified
SysOps Administrator - AWS Certified
@walterdalmut
walter.dalmut@corley.it
corley.it

3. Scalability and cost optimization with Container Services
Monolith
Container
Amazon ECS
Achievements
Summary

4. Monolith

5. ➢ Easy to manage and
easy deployments
➢ Hard to handle
workloads, hard
maintenance, hard life
for development team
➢ The technical debt
increase quickly over
the time (big legacy)

6. Scalable environment (auto)

7. ➢ Easy deployment
➢ Cost Saving on resources
➢ The technical debt
increase quickly over the
time
➢ Hard maintenance, hard
life for development team
➢ The application scale out
completely and we cannot
achieve the "scale per
feature" goal
KPI scalable systems

8. Distributed System in classical environments

9. ➢ Easy deployment cycles
➢ Cost-per-feature (scale
out per service)
➢ Scale out also the
development team
➢ So many different
environment and so many
infrastructure devices
(balancers, etc)
➢ Related costs for high
availability increases quickly
➢ Technical debt and legacy
management remains an
issue
KPI (distributed) scalable systems

10. Cluster for web applications

11. ➢ We can scale the
development team
➢ Easy and stable
deployments
➢ Reduced infrastructure
costs
➢ Costs for high availability
under control
➢ Few infrastructure parts
➢ We have to manage the
cluster
➢ Legacy and technical debt
(reduced for icroservices)
KPI Cluster

12. Power resources

13. Power resources

14. Power resources

15. Power resources

16. Power resources

17. Power resources

18. ➢ Lightweight, isolated environment for our
application
➢ Dedicated networking for our applications
➢ CAP - limits for resources (CPU, RAM)
Container

19. Container
docker run
--cpu-shares 48
--memory 32M
--network app1
ubuntu:16.04
ls -las

20. Infrastructure challenges
➢ add more microservices easily
➢ (auto)scale microservices
➢ handle constraints for microservices
➢ release microservice updates easily

21. AWS ECS
Elastic Container Service
(orchestrator)

22. ➢ Create an Application Load Balancer that proxy all
microservices
➢ AWS Certifcate Manager to support HTTPs for
microservices
➢ Prepare an autoscaling group that wrap an ECS
cluster
➢ Every microservice is an ECS Service (Docker
containers)
➢ Autoscaling group per service that scales inside the
cluster
➢ Other interesting things:
○ Create batch jobs
○ Create scheduled jobs
Create a playground for microservices with ECS clusters

23. Playground for microservices

24. ➢ Create a Target Group in the Application Load
Balancer
○ Rule on: Path
○ Rule on: Domain Name
Microservice Entrypoint on ALB

25. (Auto)Scaling Microservices

26. ➢ Dedicated resources for microservice
➢ Different autoscaling groups
Docker label/constraints for microservices

27. Docker Constraints

28. ➢ Docker Images on ECR (Elastic Container
Registry)
➢ Deployment options with ECS Deployments
○ Minimum active tasks during
deployments
○ Maximum active tasks during
deployments
Release microservice updates easily

29. Min: 100% -> Max: 200%

30. How to deploy and manage so
many services?

31. Continuous Delivery

33. ➢ Service oriented architecture
➢ Small applications (simple replacements) -
microservices
➢ Small development teams (engage different
suppliers)
○ Working In Parallel
➢ Dedicated languages per microservices
➢ Resources optimization per services
➢ Speed-up deployments
➢ Managed infrastructure with ECS (focus on app
development)
➢
Achievements

34. Thanks for listening.
AWSome Day - Torino 2018 - walter.dalmut@corley.it