Before Docker was unleashed on the world, Google already understood the concept of containers, and has been running a distributed system that allowed the company to service its application requests by running and bringing down containers on demand. To support systems of this nature, Google has spent the last 10-15 years building an advanced infrastructure across the world. Think of Gmail, Google Docs and you can imagine the millions of users at any given time. Google has been running some of the largest Web properties on the planet. In a nutshell, this is what Kubernetes is all about.
So what we need is orchestration software that provides automated container deployment, scaling and management. Infrastructure providers cannot run their data centres efficiently by simply spinning up VMs, which may end up not getting fully utilised. Similarly, from an operations point of view and, especially from a data centre angle, the days of allocating VMs and running your applications on them are gone. The challenge lies in the areas of managing the installation, rolling out upgrades, monitoring the Docker hosts and containers for their health, scaling up/down the number of containers needed as per the load and more.įrom their perspective, it is important that developers do not have to worry about infrastructure and provisioning, even if the applications that they have dockerised need to scale. In fact, it lies in the realm of distributed software, which makes it a challenge to run Docker containers at scale.
But when it comes to running large sites, one would probably need several large clusters, running thousands of nodes, if not more. So, while Docker with its easy-to-use tool set has made it convenient to launch a few containers on a single host, at best, the tooling is good enough for a few host machines running several containers on it.
0 kommentar(er)
