Presentation made at DevOpsDays Berlin 2015 Container technology are being evaluated by software developers and administrators with a great deal of interest. Developers want to focus on what they do best: Creating and coding new applications. That shouldn't have to change just because they need to deploy an application to a different environment. Administrators want the environment to stay reliable and stable, keeping changes at a minimum. By following a strategy that embraces good Architecture, use of Containers, DevOps philosophy, Apache Mesos and a Cloud based environment, developers and operators can create, consume and collaborate on the infrastructure configuration over the time, deploy Java EE applications and test your application infrastructure consistently regardless of the stage of the development life cycle.

1. Containers, DevOps, Apache Mesos and Cloud
Reshaping how we develop and delivery software
https://twitter.com/marceloancelmo
Marcelo Sousa Ancelmo
Enterprise Architect
marceloancelmo@gmail.com
marcelo.souzaancelmo@ig.com
marceloancelmo
http://www.slideshare.net/marceloancelmo
https://www.linkedin.com/in/marceloancelmo

2. Are your applications ready?

3. Decompose the applications into self-contained services
Be stateless (As much as possible)
NFR's are king, be aware on latency, throughput, etc...
Expect an impact on your application architecture
Fault tolerant
Scalable
Elastic
Multi-tenant

4. !!!MICROSERVICES!!!

5. Microservices...
… or more Spaghetti

6. “There are 17 million shipping containers in existence, packed with every
physical good imaginable. Every single one of them can be loaded onto the
same boats, by the same cranes, in the same facilities, and sent anywhere
in the World with incredible efficiency. It is embarrassing to think that a 30
ton shipment of coffee can safely travel half-way across the World in less
time than it takes a software team to deliver its code from one datacenter to
another sitting 10 miles away.”
5th
principle of Open Container Initiative -
https://github.com/opencontainers/specs/blob/master/principles.md
Why Use Containers?

7. Collaboration @ Container

8. Your usual Delivery Pipeline...

9. … Is now Baking your image

10. And potentially can use all your computing power

11. Introducing Apache Mesos
Program against your datacenter like it’s a single pool of resources
“Apache Mesos abstracts CPU, memory, storage, and other compute resources
away from machines (physical or virtual), enabling fault-tolerant and elastic
distributed systems to easily be built and run effectively.”
http://mesos.apache.org/
Used by Twitter, AirBNB, eBay, Netflix, Apple and many others
http://mesos.apache.org/documentation/latest/powered-by-mesos/

12. Apache Mesos Overview
Batch Processing Long Running Services

13. Way of work

14. Apache Mesos Architecture

15. Resource Offer example

16. Auto-Scale

17. Application
300 users

18. Autoscaling UP
600 users

19. Autoscaling DOWN
400 users

20. High Availability

21. Application Running
300 users

22. Node Failure
300 users300 users

23. Starting a new node for the application
300 users300 users

24. Application Running
300 users

25. Continuous Delivery
Blue-Green Deployments

26. Continuous Delivery – Blue / Green

27. Deploy the application
Production

28. Test the application
Production

29. Flip the application
Production

30. Empowering everyone
Production

31. Continuous Delivery
Canary Release

32. Continuous Delivery – Canary Release

33. Deploy the new version
Production
100%

34. Test and Evaluate the new version
Production
80%
Production
20%

35. Rollout the new Release

36. Putting into perspective
“If a Docker application is a Lego brick, Kubernetes would be like a kit for
building the Millennium Falcon and the Mesos cluster would be like a whole
Star Wars universe made of Legos.” ~ Solomon Hykes

38. Questions?

39. Thank You
Merci
Grazie
Gracias
Obrigado
Danke
Japanese
English
French
Russian
German
Italian
Spanish
Brazilian Portuguese
Arabic
Traditional Chinese
Simplified Chinese
Hindi
Tamil
Thai
Korean
Dziękuję
Polish
Marcelo Sousa Ancelmo
Enterprise Architect
marceloancelmo@gmail.com
marcelo.souzaancelmo@ig.com