GoDaddy Container-as-a-Service (ElasticHosts, Springs.io), discontinued vs. Kubernetes

Unlike other providers, Springs doesn’t use a pre-built container solution, instead opting for their own software built from the ground up.

Incentivized

K8s should be avoided - If your application works well without being converted into microservices-based architecture & fits correctly in a VM, needs less scaling, have a fixed traffic pattern then it is better to keep away from Kubernetes. Otherwise, the operational challenges & technical expertise will add a lot to the OPEX. Also, if you're the one who thinks that containers consume fewer resources as compared to VMs then this is not true. As soon as you convert your application to a microservice-based architecture, a lot of components will add up, shooting your resource consumption even higher than VMs so, please beware. Kubernetes is a good choice - When the application needs quick scaling, is already in microservice-based architecture, has no fixed traffic pattern, most of the employees already have desired skills.

Incentivized

• Container hosting, cloud virtualization
• Elastic capacity scaling and pay-per-use billing
• Linux kernel containerization technologies for container isolation and control

Incentivized

• Complex cluster management can be done with simple commands with strong authentication and authorization schemes
• Exhaustive documentation and open community smoothens the learning process
• As a user a few concepts like pod, deployment and service are sufficient to go a long way

Incentivized

• Provide more options at lower costs
• It would be nice to see that expanded out to more distributions. What would be potentially even better though is templates. Some hosts can deploy ready-to-run WordPress/Drupal sites, LAMP instances, ownCloud instances, etc. at the drop of a hat. If Springs could replicate this with their container hosting they’d immediately appeal to a much, much wider audience;

Incentivized

• Local development, Kubernetes does tend to be a bit complicated and unnecessary in environments where all development is done locally.
• The need for add-ons, Helm is almost required when running Kubernetes. This brings a whole new tool to manage and learn before a developer can really start to use Kubernetes effectively.
• Finicy configmap schemes. Kubernetes configmaps often have environment breaking hangups. The fail safes surrounding configmaps are sadly lacking.

Incentivized

Springs is drastically cheaper than running 4 OVH servers, and a little cheaper than running nano instances on AWS.

Incentivized

Most of the required features for any orchestration tool or framework, which is provided by Kubernetes. After understanding all modules and features of the K8S, it is the best fit for us as compared with others out there.

Incentivized

• In the beginning I wasn’t sure what I should set it to for my web server, so I left it. After a while the Average usage area begins showing how much resource the container is demanding and from that more adequate limits can be set.
• Springs is drastically cheaper than running 4 OVH servers, and a little cheaper than running nano instances on AWS.

Incentivized

• Because of microservices, Kubernetes makes it easy to find the cost of each application easily.
• Like every new technology, initially, it took more resources to educate ourselves but over a period of time, I believe it's going to be worth it.

Incentivized