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

• Deploying mesosphere and friends (e.g. marathon)
• Deploying applications (e.g. Cassandra, Jenkins, Spark) on to mesosphere
• Providing value add components such as velocity, and marathon-lb

Read full review

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

Read full review

• Setting up is a bit of a hassle, especially ZooKeeper state management and mesos and marathon quorum.
• Occasionally, I observed some failures when deploying something onto Marathon. Logging or detailed error reporting can help.
• Stale containers and inconsistent states resultant of the cluster failure are hard to solve and need a complete system restart to get it back to normal state.

Read full review

• 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;

Read full review

• I see mesosphere as having a positive impact overall on the industry trending Docker and containers in general.
• Seeing how mesosphere helps and simplifies things for the developer and ops, it is definitely a game changer.
• Native support of on demand scaling up and down as per the need is one of the best features.

Read full review

• 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.

Read full review