Containers are eating the world. If you have built and deployed an application in production over the last few years, the odds are that you have deployed your code in containers. You might have created and deployed individual containers (Docker, Linux LXC, etc.) directly in the beginning, but quickly switched over to a container orchestration technology like Kubernetes (K8s) or Swarm when you needed to coordinate multi-node deployments and high availability (HA). In this container-driven world, what will the future of the application stack look like? Let’s start with what we need from this “future” application stack.
What Do We Need From This Future Application Stack?
We want to be cloud agnostic with the ability to deploy to any cloud of our choice. Ideally, we can even mix in various providers in a single deployment.
We need to be able to run our application stack on-premise with our own custom hardware, private cloud, and internally managed datacenters.
It almost goes with saying, but I’ll add it in for completeness. The future open stack needs to support all of the popular programming languages.
The Future Application Stack
Kubernetes is a portable, extensible open-source platform for managing containerized workloads …