Accept cookies for analytics, social media, and advertising, or learn more and adjust your preferences. These cookies are on by default for visitors outside the UK and EEA. Privacy Notice.
Why you should treat infrastructure components like disposable resources
What you need to know to get started with Docker networking
How to meet the challenges of service discovery and the options currently available
How to automate routing and load balancing of your containers
Docker is one of the most exciting open source projects of recent years. By packaging the application in a container with all the other software it needs to run, Docker enables applications developed on a laptop to run in the same way on a production server.
Being in production, however, introduces a whole host of challenges that you don’t always think about in development. Now you have to worry about connectivity, load balancing to scale and handle increased load, being secure against malicious users, and sharing resources with potentially hundreds of other apps (or microservices) running in the same environment. Having a good Docker networking and service discovery architecture in place is key to being successful with your Docker‑based applications.
Michael Hausenblas is a Developer Advocate for Go, Kubernetes, and OpenShift at Red Hat, where he helps appops to build and operate distributed services. His background is in large-scale data processing and container orchestration and he’s experienced in advocacy and standardization at the W3C and IETF. Before Red Hat, Michael worked at Mesosphere and MapR and in two research institutions in Ireland and Austria. He contributes to open source software (mainly using Go), speaks at conferences and user groups, blogs, and hangs out on Twitter too much.
