This document discusses continuous delivery using containers. It describes how the company uses microservices architecture, scaling, full automation, and continuous delivery. Continuous delivery is defined as keeping software in short cycles so it can be reliably released at any time. The deployment pipeline includes committing code, running unit tests, integration tests, end-to-end tests, building Docker images, and pushing to a registry. CoreOS is also discussed as a lightweight OS that runs all services in containers and uses a distributed key-value store.

1. Continuous Deployment with Containers
David Papp @pappdav
Chief Architect @ghostmonitor
Docker nem csak fejlesztesre

2. Who are we?

3. • Established in May 2015
• The team headcount 13
• Company profile: E-Commerce

4. What technologies do we use?

6. •Microservices architecture
•Scaling
•Full automation
•Continuous Deployment & Delivery

7. What is Continuous Delivery?

8. Continuous Delivery (CD) is a software
engineering approach in which
teams keep producing valuable
software in short cycles and ensure
that the software can be reliably
released at any time.
Chen, Lianping (2015). "Continuous Delivery: Huge Benefits, but
Challenges Too". IEEE Software 32
“

9. “short cycles”

10. “released at any time”

12. Deployment pipeline
Continuous Delivery vs Continuous Deployment

13. •Commit/Push
•Unit test
•Integration test
•End2end test
•Docker image build
•Push registry

14. source: http://blog.crisp.se/wp-content/uploads/2013/02/continuous-delivery-deployment-sm.jpg

15. codeship-services.yml
codeship-steps.yml

16. CoreOS

17. • Lightweight OS based on Gentoo Linux
• Updated with regular automatic OS updates
• Has a distributed key-value store at the core
• Read-only rootfs. Writeable /etc
oAll services are in containers

18. •Distributed key/value store
•Like a directory tree
•JSON/REST API
•Uses a Discovery URL

20. Demo

21. Thanks

22. Question?