D2iQ (formerly Mesosphere) still supports the Mesosphere solution, which is designed for operations at a very large scale. It's powered by DC/OS, a production-proven cloud native platform that runs containers and data services on the same infrastructure.
D2iQ rebranded to reflect their change and broadening of focus towards Kubernetes but other services such as Cassandra, Kafka, and Spark. D2iQ also now offers IT professional services in tandem with its products.
N/A
GoCD
Score 8.0 out of 10
N/A
GoCD, from ThoughtWorks in Chicago, is an application lifecycle management and development tool.
Mesosphere is well suited for orchestrating workloads. It supports Docker as a container as well as support others. It is highly suitable for running resilient and auto recovering big data/application containers. Mesosphere has proven time and again to be production ready at a massive scale. It supports native single button/API call scale up and scale down and supports various deployment patterns like Blue-Green and others.
Previously, our team used Jenkins. However, since it's a shared deployment resource we don't have admin access. We tried GoCD as it's open source and we really like. We set up our deployment pipeline to run whenever codes are merged to master, run the unit test and revert back if it doesn't pass. Once it's deployed to the staging environment, we can simply do 1-click to deploy the appropriate version to production. We use this to deploy to an on-prem server and also AWS. Some deployment pipelines use custom Powershell script for.Net application, some others use Bash script to execute the docker push and cloud formation template to build elastic beanstalk.
Pipeline-as-Code works really well. All our pipelines are defined in yml files, which are checked into SCM.
The ability to link multiple pipelines together is really cool. Later pipelines can declare a dependency to pick up the build artifacts of earlier ones.
Agents definition is really great. We can define multiple different kinds of environments to best suit our diverse build systems.
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.
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.
GoCD is easier to setup, but harder to customize at runtime. There's no way to trigger a pipeline with custom parameters.
Jenkins is more flexible at runtime. You can define multiple user-provided parameters so when user needs to trigger a build, there's a form for him/her to input the parameters.
Settings.xml need to be backed up periodically. It contains all the settings for your pipelines! We accidentally deleted before and we have to restore and re-create several missing pipelines
More straight forward use of API and allows filtering e.g., pull all pipelines triggered after this date
