We are excited to announce the release of Operos v0.2. Even though the change from 0.1 to 0.2 may seem numerically insignificant, it represents several huge milestones for Operos.
Thanks to the trend towards microservices, backend applications are becoming more complex and distributed. Many teams struggle to accommodate these architectures with the traditional approach to deploying systems - configuration management with tools like Puppet, Chef, Ansible, or Salt. The playbooks/recipes required by these new application stacks grow in complexity until they’re no longer maintainable or comprehensible.
Enter Kubernetes. It brings with it a new hope: a standardized declarative API for doling out hardware resources and managing your containers’ lifecycle.
However, Kubernetes is not an end in itself. What most organizations need is a complete orchestration platform. Kubernetes provides a few (albeit very important) pieces of such a platform - the API server and scheduler. But, generally speaking, this is not enough.
When does it make financial sense to host services/applications in the public cloud and when in a colo? In this post, I will investigate the economics of building a cluster in a carrier hotel (colo) vs public cloud, e.g. Amazon Web Services (AWS).
Subscribe via RSS