Developed by Rancher Labs and now from SUSE, Rancher is open-source software that enables organizations to deploy and manage Kubernetes at scale, on any infrastructure across the data center, cloud, branch offices, and the network edge. Rancher centrally manages Kubernetes clusters across the organization in order to ensure security and accelerate transformation. Rancher is also available hosted. Hosted Rancher is a fully managed Rancher control plane - presented as the fastest, most cost…
$7,594.99
per year up to 500 nodes
Pricing
Apache Mesos
SUSE Rancher
Editions & Modules
No answers on this topic
Subscription license
7,594.99
per year up to 500 nodes
Standard Subscription
11,234.99
per year 10 nodes
Priority Subscription
30,514.99
per year 10 nodes
Management Server Priority Subscription
41,830.99
per year 1 instance
Offerings
Pricing Offerings
Mesos
SUSE Rancher
Free Trial
No
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Apache Mesos
SUSE Rancher
Features
Apache Mesos
SUSE Rancher
Container Management
Comparison of Container Management features of Product A and Product B
Mesos is really great when you have a big datacenter with many different applications and use cases. It will help you to optimize the resource usage, being a centralized API for your infrastructure. It will not suit well for small companies that just need to deploy a web app. In this case, I would recommend something smaller.
SUSE Rancher as a management tool becomes useful on a larger scale. Small deployments not so much. If someone also requires Kubernetes capacity or storage, Rancher is an excellent choice. Also, without Kubernetes' skills, it is unlikely that Rancher deployment is going to be a success. Then again if someone else is managing your Kubernetes capacity, setting up the software's capacity will yield greater control. Rancher is not a very integrated solution similar to others in the market.
Mesos may have many frameworks. If you have Mesos installed on your servers, you may use it for many kinds of tasks. Today we're running only web applications but the idea is to install a different framework for big data soon.
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.
No possibility to snapshot Projects. You can snapshot and restore the whole Kubernetes cluster, but not a Project or Namespace. For this, you have to use external tools.
You cannot detach the Rancher-created Kubernetes clusters from Rancher management.
Overall it deserves an 8 out of 10. The platform is very easy to use as long as the UI is stable. We have had a few buggy versions in the past. However the CLI is excellent and the platform is simple to manage and maintain. It is easy to deploy and offer for company wide use which increases utilization and ROI.
The documentation is quite complete and there is a very active community that is willing to collaborate and answer questions for those who are just starting out.
Kubernetes is by far the best choice. More reliable and better developer experience. Mesos is prone to sporadic failures and not really designed to handle CI/CD-based deployments. Docker Cloud once shut down our entire cluster for "upgrades" without giving us any warning.
SUSE Rancher is an excellent choice for managing multiple Kubernetes clusters, especially when catering to different teams with distinct access rights and requirements. It allows us to deploy these clusters on-premises across various sites or in the cloud. However, if you’re dealing with only one or a few Kubernetes clusters, using SUSE Rancher might introduce unnecessary complexity. This is where EKS wins, as its native cloud based abilities are better suited to scale, support higher complexity and larger demand.
Shortens "Time-to-Market" factor for new business applications or implementing new functionalities. From 1 to 50 microservices-based business applications in 6 years.
24/7 availability, generates more money. There are many infrastructure components that are regularly powered-off for maintenance or upgrade, bur we rarely are turning off our downstream Kubernetes clusters where our business applications lives.
Single Point of Contact with platform maintenance and development Team, eases implementation of new business applications
