The signs of cloud maturity are all around us. We see survey after survey showing us that companies are moving more and more workloads to the cloud. As that happens, organizations are looking for more standard ways of doing things, and the industry is answering.
For instance, at OpenStack Summit in Vancouver in May, the organization that runs OpenStack announced a certification program for any product that wants to appear in the OpenStack marketplace. It ensures that these programs meet a minimum level of interoperability to be called an OpenStack product.
OpenStack is the open source alternative that was originally created by RackSpace, NASA, and others as a check against the growing power of Amazon Web Services. Companies liked the idea of Infrastructure as a Service but wanted more control over the process than AWS was willing to share.
The community has grown quickly, and this growth forced them to find a more standard way of defining which applications are going to be called OpenStack to avoid confusion in the marketplace. This is particularly important as larger organizations get involved with the project. But, it's also critical for smaller organizations that need a way to know what they are using and that it meets a minimum standard, so they can continue to use the same tools as they grow.
Container Standards Too
Just this week at DockerCon, Docker, CoreOS, Google, Microsoft, Amazon, and others agreed to a common container standard. This is a big deal because with so many competing container types, this has been a problem for everyone involved, from customers to vendors to third parties who make tools to support the containers.
Containers are a way of delivering micro services or small discrete pieces of applications. It's worth noting that Docker and CoreOS are open source projects. In the past, developers created one monolithic application on a single server. Today's applications are made up of smaller pieces, and they're distributed across multiple servers.
Having a common container standard spares everyone involved from having to understand different types of containers. With a base everyone agrees to, vendors can build on top of that and differentiate themselves on the individual company's products and services. It saves everyone the headache of trying to get different containers to work together or buying tools to manage different container types. Every tool should work with every type of container from member companies.
These are just two examples of industry groups or vendors trying to agree on some common core principles. It helps everyone avoid the pain of figuring out multiple ways of doing things while trying to get them to work together, as well as with other tools in the enterprise.
As the cloud matures, there's more demand for this type of standardization, and the industry as a whole is trying to find ways to deliver it.