Hardware hypervisors were a first-generation approach to the challenges of resource and security isolation, but they’re unnecessarily shackling the future of containers. By double-wrapping our containers in VMs, we’re losing both performance and convenience. And by using container runtime environments that don’t offer a full network stack to each container, we’re just adding complexity and frustration.
This can be solved: implementing container-native infrastructure addresses the operational challenges of container-based application deployment. It solves for convenient networking, stronger scaling, and strengthened security. In this session, Joyent CTO Bryan Cantrill will pull from his experience of running containers in production for over a decade, to delve into the negative consequences of continuing to utilize a hardware hypervisor layer and the benefits of running containers directly on multi-tenant bare metal.
Bryan Cantrill is CTO at Joyent. Previously a Distinguished Engineer at Sun Microsystems, Bryan has spent over a decade working on system software, from the guts of the kernel to client-code on the browser and much in between. Bryan led the team that designed and implemented DTrace, a facility for dynamic instrumentation of production systems that won the Wall Street Journal’s top Technology Innovation Award in 2006 and the USENIX Software Tools User Group Award in 2008. Bryan co-founded the Fishworks group at Sun, where he designed and implemented the DTrace-based analytics facility found in the Sun Storage 7000 series of appliances — a facility that InfoWorld described as “stunning” in a February 2009 review. In 2005, Bryan was named by MIT’s Technology Review as one of the top 35 technologists under the age of 35, and by InfoWorld as one of their Innovators of the Year. Bryan received the ScB magna cum laude with honors in computer science from Brown University.
©2015, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com