Following the announcement of the first batch of speakers for DockerCon Europe last week, we’re happy to announce 4 additional sessions today. Stay tuned for the final lineup of speakers!
Here is the list of speakers who have been chosen by the DockerCon program committee this week:
Session title: Revamping Development and Testing Using Docker
Abstract: Docker doesn’t only revolutionize your application hosting, it also revolutionizes your development pipeline. In this talk I want to show how ING uses test containers for confidence checks, application containers to integration test both dependant services and services we depend on. I will also show how you can go to master-only development and create D/T
environments for every feature branch easily using docker, a reverse proxy and a CI server. Because ING as a bank has a lot of complexity in the IT, Docker offers us a lot when it comes to integration testing services, because test environments have become so much cheaper.
Session title: Migrating a large code-base to containers
We want to run our code as a collection of small collaborating containers, but we have a large existing code-base, and don’t want massive disruption to product releases.
We’ll take a walk through some of the challenges we’ve faced, and techniques used to solve taking a set of large collaborating Rails applications into containers. In this process we’ve aimed to progressively move towards our ideal.
Joe Brown – Engineer at Weeby.co
Session title: Scaling Development Environments with Docker
Abstract: We set out to solve the problems of quickly building high quality games for a fragmented mobile market. Taking advantage of HTML5 allowed a fast, familiar and highly iterative local development process, and a hybrid build process for native apps meant high performance games on mobile. Our product is designed to comprehensively handle complex UI flows, related server tasks as well as deep integrations with any social platform. This is necessarily complex piece of engineering, with dozens of large dependencies, and 5 local web servers powering a single user’s experience. When we set out to make this easily available to 3rd parties, we used Docker to solve to major challenges: 1) Fitting many users, each with a unique development environment, on to one machine; 2) Managing all of these development environments in a scalable way.
Once again, we would like to thank all of those who took the time to submit talks!