Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Docker - Build, Ship and Run Any App, Anywhere Hollywood edition


Published on

Since I presented this inside a movie theater I reference a few movies. This talk covers the Why of Docker more business case relevant, the VM vs Containers argument and Swisscom use cases with Docker

Published in: Technology
  • Free Shed Plans, 12000 SHED PLANS. FREE SHED PLANS CLICK HERE ✤✤✤
    Are you sure you want to  Yes  No
    Your message goes here

Docker - Build, Ship and Run Any App, Anywhere Hollywood edition

  1. 1. Agenda • Introduction • Why Docker? • Containers vs VM’s • Use Case • Demo 2
  2. 2. Brian Christner / @idomyowntricks > Swisscom Cloud Architect > Background in Containers, Cloud, & Engineering > Docker Captain About me
  3. 3. Agenda • Introduction • Why Docker? • Containers vs VM’s • Use Case • Demo 4
  4. 4. Monitoring & Docker Swarm Overview
  5. 5. 6 The application landscape is changing Loosely Coupled Services Many Small Servers or devices ~2000 Today Monolithic Big Servers Slow changing Rapidly updated
  6. 6. Development VM QA Server Public Cloud Disaster Recovery Contributor’s Laptop Production Servers Production Cluster Data Center Containers are the catalyst Static Website Web Front End Background Workers User DB Analytics DB Queue API Endpoint
  7. 7. 8 Docker delivers innovation, speed and savings + +Agility Portability Control State of App development Survey: Q1 2016, Cornell University case study 13XMore software releases 62%Report reduction in MTTR 10XCost reduction in maintaining existing applications Eliminate “works on my machine” issues 41%Move workloads across private/public clouds 65%Reduction in developer onboarding time
  8. 8. Long vs Short Lived Apps/Containers Long Lived Short Lived
  9. 9. VM’s
  10. 10. Reduce Costs & Streamline Operations Containers and VMs together: • Optimize: Added flexibility in using infrastructure resources • Consolidation: Greater workload density across existing servers. • Reduce Costs: Lower OS and VM licensing CapEx and reduce OpEx costs to support and maintain smaller infrastructure Before: One service and OS per VM After: One container per service. Multiple containers running per VM Virtualization Bins/Libs App OS Bins/Libs App OS Bins/Libs App OS Virtualization Bins/Libs App OS Virtualization OS Bins/Libs App Docker Engine Bins/Libs App Bins/Libs App Bins/Libs App
  11. 11. Container Separation Oscar the Ops Guy Worries about what’s “Outside the Container” - Logging - Monitoring - Networking All containers work the same way (Start, Stop, etc) Dan the Developer Worries about what’s “Inside the Container” - Code - Libraries - Package Manager - Data All the servers look the same
  12. 12. 22 Frictionless across environments Dev Test / QA Staging Production Same code in dev runs unchanged in every environment Container, network, storage portability Services Networks Volumes
  13. 13. 23 VM VM VM
  14. 14. Swisscom Developer Portal Home for innovators and passionate developers
  15. 15. Let’s have a look: DEMO
  16. 16. Great Docker Resource – My Docker Projects – Docker Resources
  17. 17. • Workshops • Architecture • Training More Docker!