Docker seems the perfect infrastructure for Microservices. However, PaaS like Amazon Elastic Beanstalk or Cloud Foundry might be interesting alternatives. This talks shows how PaaS support Continuous delivery. Held at Continuous Lifecycle 2015.

1. Infrastructure for Continuous
Delivery & Microservices: PaaS or
Docker?
Eberhard Wolff
Fellow
@ewolff

3. http://microservices-buch.de/ http://microservices-book.com/

4. Why This Talk?
> 2008: Google App Engine
> Google Infrastructure for the masses!
> 2010: Selling PaaS into Enterprise
> Future of application development!
> Didn‘t really take off

5. What is Cloud?

6. Cloud = Self Service

7. Infrastructure
as a Service
Platform
as a Service
Software
as a Service
Software or Service
that you use
Components that
you integrate into
your app
Virtual Application
Server
Handles Scale-Out
Mostly Managed by
Provider
Virtual Servers
Manage Everything
Yourself

8. PaaS
Your application
Including database, scaling,
monitoring, HTTP handling...

9. Cloud might be...
> Private / internal “on premise”
> Public “off premise”

10. Why PaaS?
> Scaling?
> Pay-as-you-go?
> Quickly and easily deploy applications
?

11. Continuous Delivery is
the value propostion
of PaaS

12. Issues With PaaS
> Standardized infrastructure
> Not flexible
> Hard to migrate existing applications
> Installing PaaS on-premise hard
> Enterprise=On-Premise
> Huge success for Internet apps

13. PaaS
Your application

14. Continuous Delivery:
Build Pipeline
Commit
Stage
Automated
Acceptance
Testing
Automated
Capacity
Testing
Manual
Explorative
Testing
Release
Deploy Deploy Deploy Deploy
Automated
Reproducible
Fast

15. Continuous Delivery:
State of the Art
> Roll your own deployment automation
> Chef, Puppet, Ansible
> Use some kind of virtualization
> ...or Docker

16. Docker
> No true virtualization
> Linux Containers (lxc)
> Shared kernel
> Separate file systems
> Separated network interfaces

17. Docker File Systems
> Storage backends
> Devicemapper (block devices)
> Read only base images
> + Read/write image
> Can be stacked Ubuntu
Java
Application
Read / Write

18. Docker = Lightweight
> One base image
> Other images are just a diff
> Little storage
> Kernel etc. shared
> Almost no overhead over a process
CPU

19. Docker =
Simple Deployment
RUN COPY

20. Docker =
Simple Deployment
> Dockerfile
> Just a shell script
> Behind the scenes: Optimization
> Every Dockerfile line = filesystem snapshot
> Reuse snapshots for all other Dockerfiles

21. Docker‘s History
> Public PaaS must separate tenants
> Ideally multiple tenants per VM
> Docker started as foundation for dotCloud PaaS
> Docker and PaaS related

22. Why Docker Over PaaS?
> Still simple deployment
> Still simple installation
> Unlimited flexibility

23. Your application
Load Balancer
Log Parser
Cache
Monitoring
Database

24. Microservices

25. Definition
Microservice
> Independent deployment unit
> Separate data handling & storage
> Should include UI
> Process
> VM
> Docker container
> Any technology
Server
Micro
Service

26. Operations
> Operating 50-100 Microservices?
> Huge challenge
> Only option: Standardize

27. Your application
Load Balancer
Log Parser
Cache
Monitoring
Database
Standardize
✓
✓
✓
??

28. Standardized
Environment?

29. Congrats on Building
Your Own PaaS!

30. Demo: Elastic
Beanstalk

31. Amazon Elastic
Beanstalk
> Application:
Contains all versions & environments
> Version:
Deployabel artifact
> Environment:
Runs a version of the application

32. Elastic Beanstalk
Features
> Supports multiple environments
> Blue/green deployment support
> Scalable infrastructure
> Log files stored in S3
> Monitoring through Cloud Watch
> Also via CLI, API or Cloud Formation

33. But just a WAR
is not enough

34. Elastic Beanstalk
Turn Key
Components
Paas Flexibility
Modify Beanstalk
Image
Beanstalk
+Docker
Elastic
Beanstalk
Java, Go, Python...
Databases
(RDS)
ElastiCache ...
You own
EC2 Virtual Machine
Additional
Services

35. But I want to run in my
datacenter!

36. Cloud Foundry
> Open Source PaaS
> Foundation for IBM Bluemix, Pivotal CF ...

37. Cloud Foundry
Included Services
e.g. MySQL...
Paas Flexibility
Your own
Buildback
Cloud Foundry
Buildpacks
Java, Node, Ruby, Go
You own
Service
Additional
Services

38. Demo: Cloud Foundry

39. Conclusion

40. Conclusion
> Continuous Delivery = PaaS Value Proposition
> PaaS lacked flexibility
> Docker orignates from PaaS
> Microservices = Standardization
> Standardization = Your Own PaaS
> Buy instead of build?
> Modern PaaS provide the needed flexibility

41. Thank You!
@ewolff