Making Open Work
May 8–9, 2017: Training & Tutorials
May 10–11, 2017: Conference
Austin, TX

To contain or not to contain

Jeremy Eder (Red Hat)
4:15pm4:55pm Thursday, May 11, 2017
Architecture
Location: Ballroom G
Level: Intermediate
Average rating: ***..
(3.50, 4 ratings)

Who is this presentation for?

  • System architects, system administrators, and security architects

Prerequisite knowledge

  • Basic knowledge of virtual machine and container technologies

What you'll learn

  • Learn the differences between containers and virtualization, where they complement each other, and how the two should (and shouldn't) be used together

Description

It’s a common misconception that containers and virtualization are the same thing. The truth is that although containers and virtualization have a lot in common, they often serve different use cases.

Like virtual machines, application containers keep all components of an application together, including the libraries and binaries on which they depend. By combining the ability to isolate applications with lightweight and image-based deployment capabilities, you can put more applications on a single machine and start them up much more quickly. More simply, virtual machines deliver compute resources, while containers aid application deployment and management; virtualization provides flexibility by abstraction from hardware, while containers provide speed and agility through lightweight application isolation. So instead of thinking of containers as replacing VMs, organizations should be thinking about containers as a complement to VMs—with the workload determining what to use and when.

Jeremy Eder explains that to get the most out of these important technologies, you must understand all the ins and outs of each and how they work together (and how they don’t). Jeremy compares and contrasts containers and virtualization, discusses where they complement each other, and walks you through use cases that demonstrate how the two should (and shouldn’t) be used together.

Photo of Jeremy Eder

Jeremy Eder

Red Hat

Jeremy Eder is a senior principal software engineer at Red Hat Performance Engineering, where he specializes in measurement and analysis of performance metrics and using that analysis to guide performance-tuning of real-world infrastructure and leads a high-output team of engineers focused on performance, scalability, and capacity planning of container-based infrastructures in the Atomic and OpenShift family of Red Hat products, including the application of these next generation technologies to the high-performance space. Jeremy has over a decade of experience in the financial services space, focusing on extreme low-latency architecture design, tuning, and jitter analysis. He is the author of Low Latency Performance Tuning for Red Hat Enterprise Linux 6 and 7. Jeremy is a contributor to Kubernetes, Docker, and the Linux kernel in a variety of areas where things need to go fast. He was a recipient of the 2014 Red Hat Chairman’s Award.