Mesosphere: The perfect starter kit for the Mesos ecosystem
April 01, 2016

Mesosphere: The perfect starter kit for the Mesos ecosystem

Anonymous | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with Mesosphere

I personally straddle the line between dev-ops and development, and I think mesosphere and friends adds value to both of those roles. From the dev-ops perspective using a mesosphere foundation allows for applications to be treated in a uniform way, and deployed in an efficient manner across a cluster. It's also easy to scale out. From a development perspective it puts a certain amount of dev-ops power in my hands which I would otherwise have to rely on dev-ops to do (e.g. install a particular version of node.js on these servers). It's a win-win all around. There are some issues in terms of the dev org, deploying things that the dev-ops org isn't fully up to snuff on support, so this aspect is the main challenge in my mind around the docker/scheduler paradigm. What mesosphere brings to the table is a packaged deployment solution for mesosphere and "frameworks" that facilitate deployment of various applications onto the mesosphere grid. Deploying mesosphere and various applications on top of it can be non trivial, so Mesosphere datacenter operating system (DCOS) can help a great deal with that.
  • 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
  • There isn't any specific support for upgrading (DCOS) when running in AWS. You basically have to create a new vpc and figure out how to get all your Marathon jobs from the old instance to the new instance. I think some kind of a backup/restore operation against Marathon could be helpful there.
  • Occasionally, I will experience silent failures when deploying something onto Marathon. I think an easier way to track down failures would be helpful.
  • There are some features that are reserved for the licensed enterprise offering, but in some cases, I think the feature (e.g. security) is fundamental, and it may lead to the tech being avoided because it doesn't have enough momentum to get the customer hooked. I would like to see more features provided with the open-source version and reserve licensing for support.
  • I see mesosphere as having a positive impact overall. Having experienced Docker and mesosphere, I would not want to return to the traditional way of doing things.
I happen to like mesosphere because it integrates well with a Jenkins based workflow, Deis is a little more Heroku like and it's not clear how to fit that model into a continuous-integration process. Kubernetes has also been criticized for being complicated.
I think right now Mesosphere is newer to Windows environments and has some challenges with stepping in to big data scenarios where YARN is currently being used.