We discuss the use cases for adopting Kubernetes technology. One example we reference is a small bank in Ohio that has found its own business use-case for Kubernetes. Originally, Kubernetes was built to manage Google-sized technology, so it may come as a surprise that such a small brick and mortar bank, just starting with web and mobile, would have found a reason to apply the technology. However, after identifying unexpected spikes of web traffic every Friday, the company realized that Kubernetes would provide tremendous value in addressing their problem.
We also look at the state of the big three orchestration engines: Kubernetes, Mesos and Swarm. Mesos began in 2014 as a container scheduler that Twitter was using to manage its own containers. They released it as open-source and a community began to form, focusing on big data elements. To this day, Mesos is still the preferred technology to run big data applications.
Kubernetes began as Google’s Borg technology, used internally before it was released to open-source. This technology focuses on batch use-cases and container use-cases. Kubernetes has gained a very strong community and is better suited to work with many different types of applications.
Finally, Docker came out with Swarm as a way to compete in the market. They keep things as simple as possible to get a few containers clustered together. Swarm has evolved to work mostly around Docker’s data center products. Tracking this industry over time reveals how container use cases have evolved for companies of all sizes.