GoDaddy Container-as-a-Service (ElasticHosts, Springs.io), discontinued vs. IBM Cloud Managed Istio

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

Incentivized

Clearly, the [IBM Cloud Managed Istio] tool is very useful when you have multiple services and each service is connecting with other services through APIs in different networks. To manage this type of complex network, [IBM Cloud Managed Istio] is very useful. It comes with a license that can increase the billing of your project so make sure if your application network mesh, monitoring cannot be managed on your own then you can use it. If your application is not very complex then you have many tools available like Grafana, Prometheus, Sumo Logic, which you can integrate individually with your cluster and implement. In this type of scenario, it is better to not use [IBM Cloud Managed Istio] and it will serve your purpose as well.

Incentivized

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

Incentivized

• Layers transparently onto existing applications
• Allows control of access and rules to be developed
• Creates metrics for usage

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

• Some more functionalities added could improve it better.
• Better technical user guidance.

Incentivized

Training and usage support available

Incentivized

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

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

• It reduced the complexity of network mesh (ingress/egress services).
• One tool with many solutions. No need to integrate monitoring tools or notification tools.
• It reduced the number of lines of YAML code.
• It reduced the number of labor hours.

Incentivized