As containers move from the developer's workstation into production environments there are many questions about how they fit into a company's existing infrastructure. Should a workload run in a VM or in a container? Should that container run on physical or virtual? In the data center or in the cloud? The reality is that there is no "right" answer, just a series of questions that admins should be asking as they look to figure out where to run their application workloads. In this talk we'll take a look at the key differences between containers and VMs. From there we'll discuss the coexistence of VMs and containers, and finally we'll take a look at key factors to consider when making the decision where to run your applications. Throughout the presentation we'll highlight real world customers, their problems, and their ultimate deployment decisions.

1. Containers & Clouds & VMs: OH My
Mike
Coleman
Technology Evangelist
@mikegcoleman

2. Who Am I?
• Technology evangelist at Docker
• Former: Puppet, VMware, MSFT, Intel, and HP
• First half of my career was in IT
• Second half in product management and
technical marketing
• @mikegcoleman (but mostly soccer)

3. So why are you sitting here today
• Containers vs. VMs?
• Physical vs Virtual?
• Virtual vs. Cloud?
• Cloud vs. Physical?

4. VMs
4

5. Containers
5

6. They’re different, not mutually exclusive
6

7. Just answer the question . . .

8. Besides, you won’t like the answer
http://nextgenerationgardener.blogspot.com/2013/03/building-show-garden-gathering-it-all.html

9. So many variables
• Performance
• Security
• Scalability
• Existing Skillsets
• Costs
• Etc.
http://people-equation.com/do-your-words-encourage-or-deflate/math-equation_chalkboard/

10. Points to Ponder, People
• Capacity
• Mixed Workloads
• Latency
• Disaster Recovery
• Licensing Costs
• Existing Automation
Frameworks
• Resource Pools /
Quotas
• Multi-tenancy

11. Why even start?
• Faster deploy times
– Build vs. Run time
• Simplified dependencies
• Unified tool chain
• Identical environments
• API automation

12. Reduce costs and 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
12
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

13. Migrate any workload anywhere
Infrastructure agnostic platform
• Standardize: Docker abstracts away
the infrastructure and virtualization
away from the standardized app
containers
• Portability: Containers move
without friction from one environment
to another – no recoding needed
• Lift and Shift: Containerize legacy
and microservices to gain portability
13
Bins/Libs
App
OS
Bins/Libs
App
OS
Bins/Libs
App
OS
Bins/Libs
App
Bins/Libs
App
Bins/Libs
App
OS
Docker Engine
OS
Docker Engine

14. After
Centralized CaaS for DevOps and micro services
transformation
Teams request into central IT maintained
portal/registry to provision infrastructure
and pull base images
14
App Service App Service
App A App B
Auth
…more
App Reg
Marketplace
Logging
Auth
Session
…more
App Reg
Logging
Before
App BAuth
App Reg Marketplace
Logging
App Service
Application Teams
Universal Control Plane
App AAuth
App Reg Marketplace
Logging
App Service
App BAuth
App Reg Marketplace
Logging
App Service
App AAuth
App Reg Marketplace
Logging
App Service
Portability
Authorization
App Registration
Session
Management
Marketplace
Integration
Logging
…more
Trusted Registry

15. ING delivers value faster
Challenge
• 9+ months to deploy to production
• Poorly rated applications
• Redundant processes and apps
Solution
• Continuous Integration with Docker Engine and Registry open
source and adopt DevOps
Benefits
• Ready to deploy in 15 minute
• 1,500 deployments per week
• 180 DevOps teams
• CD pipeline transformed in 4 month
15

16. Gilt deploys over 100X a day
Challenge
• From dev-to-deploy: weeks
• 7 Monolithic apps
• Wasted time implementing monolithic IaaS and PaaS
Solution
• Continuous Delivery with Docker Engine open source and private repos on
Docker Hub
Benefits
• From dev-to-deploy in minutes
• 400+ microservices
• 100+ innovations a day
• Easily burst to cloud burst at peak shopping times
16

17. Dockerizing Monoliths
• Microservices to Monoliths continuum
• Monoliths and Microliths
• Focus on the real challenges
– static configs, fixed ports, multiple processes
• Start somewhere . . .
• End up somewhere else

18. What’s the Right Tool for the Job?

19. So, what’s next
• Pick a project
• Get your hands dirty
• Mistakes may be made
• Join the community

20. Thank you!