Patterns in a Containerized World
•
0 likes•229 views
Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1UpUmV1. Matthias Luebken gives an overview of typical patterns that he has seen in developing, deploying and operating applications that leverage containers. He talks about defining best practices around a good modular container and approaches different composition strategies. He concludes in a first set of patterns like side-car / side-kick, ambassador, adapter and chains. Filmed at qconlondon.com. Matthias Luebken is the product guy (tm) at Giant Swarm. He has long time experience with different aspects in product and software development.
Recommended
Recommended
More Related Content
More from C4Media
More from C4Media (20)
Recently uploaded
Recently uploaded (20)
Patterns in a Containerized World
- 2. InfoQ.com: News & Community Site • 750,000 unique visitors/month • Published in 4 languages (English, Chinese, Japanese and Brazilian Portuguese) • Post content from our QCon conferences • News 15-20 / week • Articles 3-4 / week • Presentations (videos) 12-15 / week • Interviews 2-3 / week • Books 1 / month Watch the video with slide synchronization on InfoQ.com! https://www.infoq.com/presentations /patterns-applications-containers
- 3. Purpose of QCon - to empower software development by facilitating the spread of knowledge and innovation Strategy - practitioner-driven conference designed for YOU: influencers of change and innovation in your teams - speakers and topics driving the evolution and innovation - connecting and catalyzing the influencers and innovators Highlights - attended by more than 12,000 delegates since 2007 - held in 9 cities worldwide Presented at QCon London www.qconlondon.com
- 4. @luebken
- 5. “ Easily create lightweight, portable, self-sufficient containers from any application.”
- 6. “App Container (appc) is a well-specified and community developed specification for application containers. ”
- 7. nginx Proxy Rails Frontend A Go Backend A Node Backend An Application
- 8. Independently releasable Separate processing types Different loads Different teams Reuse Crash isolation Use differentlanguages / versions / libraries POCs
- 9. How does a good building block look like? How do we assemble them?
- 10. Related Work • 12factor.net apps • Cloud-native application architectures: Matt Stine Free Ebook • Microservices • Continuous Delivery
- 11. Container Patterns •For designing “cloud” applications. •Container runtime agnostic. •Are there general applicable patterns? •How would we describe them? •What are concrete examples and best-practices?
- 14. How does a good building block look like? How do we assemble them?
- 16. A “Module-Container” is a well behaving building block in the architecture of an application.
- 17. A Module Container is 1. Linux process 2. API 3. Descriptive 4. Disposable 5. Immutable 6. Self-contained 7. Small
- 18. 1. Linux Process
- 19. 1. Linux Process • React to signals • Return exit codes • Use standard streams • Handle arguments Examples: module-container.md#1-linux-process
- 20. 2. API
- 21. 2. API • ENV variables • Available ports • Volume mounts • Lifecycle hooks Examples: module-container.md#2-api
- 22. 3. Descriptive
- 23. 3. Descriptive • Use standard labels (e.g. proposal generic labels) • url, summary, vcs-url … • Use custom labels: • api.ENV • api.EXPOSE • api.LINKS Examples: module-container.md#3-descriptive
- 26. 4. Disposable
- 27. 4. Disposable • Don’t rely on a particular instance • Be aware of shots at your cattle • Be robust against sudden death Examples: module-container.md#4-disposable
- 28. 5. Immutable
- 29. 5. Immutable • Don’t change your container after build • Strive or a dev/prod parity Examples: module-container.md#5-immutable
- 31. 6. Self-contained • Add dependencies on build time • Sensible defaults Examples: module-container.md#6-self-contained
- 32. 7. Small
- 33. 7. Small • Don’t use large base images • Use the minimal footprint e.g. Alpine Examples: module-container.md#6-small
- 34. Recap: A Module Container is 1. Linux process 2. API 3. Descriptive 4. Disposable 5. Immutable 6. Self-contained 7. Small
- 35. How does a good building block look like? How do we assemble them?
- 38. A group of closely related containers. Deployed as a single unit and share namespaces.
- 40. Pattern: Sidecar / Sidekick Enhance & extend the main container. K8S: transparently. Netflix: platform features. UDSA Node Backend MAIN CONTAINER Redis Cache SIDECAR Pod
- 42. Pattern: Adapter Standardise and normalize output. E.g. logging and metrics. localhost or A Node Backend MAIN CONTAINER Logging Adapter ADAPTER Pod
- 44. Proxy a local connection to the world: Service Discovery, Client Side LB, Circuit Breaker A Node Backend MAIN CONTAINER Service Discovery AMBASSADOR Pattern: Ambassador localhost (Pod)
- 45. Pattern: Container chains Defined order of starting and stopping sidecar containers. A Node Backend MAIN CONTAINER Storage Config SIDECAR Discovery SIDECAR Network Config SIDECAR (Pod)
- 46. Summary: Container Patterns QCON 08.03.2016 Module container 1. Linux process 2. API 3. Descriptive 4. Disposable 5. Immutable 6. Self-contained 7. Small Composite • Sidecar • Adapter • Ambassador • Chains How does a good building block look like? And how would you assemble them? github.com/luebken/container-patterns @luebken
- 48. Credits • https://www.flickr.com/photos/skynoir/8241460998 (Cover image) • https://www.flickr.com/photos/amlz/8664728590 (Lego) • https://www.flickr.com/photos/guidedbycthulhu/6810361241 (Socket) • https://www.flickr.com/photos/seektan/2074853585/ (Label) • https://www.flickr.com/photos/gullevek/2122873934 (Trash) • https://www.flickr.com/photos/grantmac/4852826923 (Lock) • https://www.flickr.com/photos/mhirano/13236048424 (Hand)
- 49. Watch the video with slide synchronization on InfoQ.com! https://www.infoq.com/presentations/patterns- applications-containers