Completely unreliable and doesn't fit with modern workflows
Pros
- Mesos let us orchestrate containers on our own hardware using our own DNS. We switched from Docker Cloud, which caused several major outages for us.
Cons
- Unreliable deployments that would fail for no good reason. Sometimes our Docker container would be "restarting" forever because Mesos thought it didn't have enough resources to start the container.
- Impossibly slow UI. Built in React under the hood with a lot of bloatware backed in, so loading the Mesos UI on a slow internet connection was painful.
- No real logging solution - it would stream "console.log()" output to the UI, but searching for logs wasn't really possible without downloading a huge file.
- No built-in support for redeploying containers from a CI. We had to create a service whose whole job was to expose an HTTP endpoint that restarted a container, and then made Circle CI ping the endpoint whenever we wanted to redeploy.
Return on Investment
- Developers needed to spend hours waiting to verify that their supposedly automated CD deploys actually went through.
- Lots of late night and early morning calls that Mesos deploys are hanging again.
- 10-20 hours spent building a custom service just to integrate Mesos with a CD provider.
Alternatives Considered
Google Kubernetes Engine and Docker
Other Software Used
MongoDB, MongoDB Atlas, GitHub
