Apache Mesos vs. Google Cloud Run

There's really no reason to ever use Mesos. We switched over to Kubernetes and it's been a breath of fresh air - better CD support, easy CLI for browsing logs, no mysterious dangling redeploys. If you're looking for a tool to manage a fleet of Docker containers on VMs, Kubernetes beats Mesos by a wide margin.

Incentivized

Microservices and RestFul API application as it is fast and reliant. Seamless integration with event triggers such as pubsub or event arc, so you can easily integrate that with usecases with file uploads, database changes, etc. Basically great with short-lived tasks, if however, you have long-running processses, Cloud Run might not be idle for this. For example if you have a long running data processing task, other solutions such as kubeflow pipelines or dataflow are more suited for this kind of tasks. Cloud Run is also stateless, so if you need memory, you will have to connect an external database.

Incentivized

• 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.
• There is a good community growing around it.

Incentivized

• Auto scaling is the best one
• provide direct VPC connectivity and rigid network
• Cloud SQL and Pub/Sub services
• Handling latency issues

Incentivized

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

Incentivized

• The UI can be made simpler. Currently the UI is bloated and it takes time to find out what you want
• More integrations with container registry providers (ECR, dockerhub)
• Better permissions UX. Currently GCP requires service accounts to be used with cloud products, the experience adding/removing permissions is difficult to navigate

Incentivized

We definitely need to renew it because we dont own our own infrastructure and storage and we are happy with Cloud Run features

Incentivized

The UI/console is great... the documentation is top-notch for developers, but the CLI itself when you have to script around it is very complex and easy to forget some options... the downside of a generic command line client.

Incentivized

Not seen any major issues when we run applications its good

Incentivized

Initially we felt slow but slowly it picked up and easy to manage

Incentivized

No real support channel, the Mesos GitHub issues list was the only one we found and it wasn't particularly helpful.

Incentivized

I was involved in the initial implementation setup, Its easy with the given documentaiton we can do ourself. Not that critical

Incentivized

Kubernetes is really great and their community is growing really fast (Google influence). We evaluated it in the beginning and it would fit for our web applications workload. We decided to proceed with Mesos because it has more potential. You may use a different framework for different kinds of tasks on Mesos. There is a Kubernetes framework for Mesos, by the way.

Incentivized

AWS Lambda supports code zip package, enabling lower cold start time. Also, AWS Lambda pricing is much simpler, easier to understand.

Other than that, the 2 products are very similar, including the Docker image support: the image must be built based on proprietary base image.

Obviously, if your other services are running in GCP, then Google Cloud Run is your only choice for tight integration, & private networking.

Incentivized

Not part of purchase.

Incentivized

It has good auto scale feature and reliable also

Incentivized

We have very good support when needed

Incentivized

• It's optimizing our resources.
• It's improving our process. This argument is not just for Mesos, but we needed a tool like this to start changing and it works like a charm.
• It's open source.

Incentivized

• Built in support for auto scaling helps reduce operational overhead
• Any application performance issues can be addressed quickly by allocating more resources while a proper fix can be planned and rolled out later
• Using Google Cloud Run enables development of microservices which provides granular control for scaling critical services in the platform

Incentivized