Nearly 10 TIMES faster system resets – that’s the result of fully enabling an multi-container immutable deployment on Digital Rebar.
I’ve been having a “containers all the way down” month since we launched Digital Rebar deployment using Docker Compose. I don’t want to imply that we rubbed Docker on the platform and magic happened. The RackN team spent nearly a year building up the Consul integration and service wrappers for our platform before we were ready to fully migrate.
During the Digital Rebar migration, we took our already service-oriented code base and broke it into microservices. Specifically, the Digital Rebar parts (the API and engine) now run in their own container and each service (DNS, DHCP, Provisioning, Logging, NTP, etc) also has a dedicated container. Likewise, supporting items like Consul and PostgreSQL are, surprise, managed in dedicated containers too. All together, that’s over nine containers and we continue to partition out services.
We use Docker Compose to coordinate the start-up and Consul to wire everything together. Both play a role, but Consul is the critical glue that allows Digital Rebar components to find each other. These were not random choices. We’ve been using a Docker package for over two years and using Consul service registration as an architectural choice for over a year.
Service registration plays a major role in the functional ops design because we’ve been wrapping datacenter services like DNS with APIs. Consul is a separation between providing and consuming the service. Our previous design required us to track the running service. This worked until customers asked for pluggable services (and every customer needs pluggable services as they scale).
Besides being a faster to reset the environment, there are several additional wins:
- more transparent in how it operates – it’s obvious which containers provide each service and easy to monitor them as individuals.
- easier to distribute services in the environment – we can find where the service runs because of the Consul registration, so we don’t have to manage it.
- possible to have redundant services – it’s easy to spin up new services even on the same system
- make services pluggable – as long as the service registers and there’s an API, we can replace the implementation.
- no concern about which distribution is used – all our containers are Ubuntu user space but the host can be anything.
- changes to components are more isolated – changing one service does not require a lot of downloading.
Docker and microservices are not magic but the benefits are real. Be prepared to make architectural investments to realize the gains.
Pingback: Faster, Simpler AND Smaller – Immutable Provisioning with Docker Compose! | Rob Hirschfeld
Pingback: 2015 Container Review |
Pingback: Hey Dockercon, let’s get Physical! | Rob Hirschfeld
Pingback: LinuxKit and Three Concerns with Physical Provisioning of Immutable Images | RackN