Likelihood to Recommend It is well suited when you want to have a
Kubernetes cluster in AWS Cloud and want to avoid all the management overhead of maintaining your own cluster in terms of the control plane. EKS seems to be lacking in features when compared with AKS and GKE. Backups, service mesh, and monitoring have a lot of room for improvements.
Read full review 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.
Read full review Pros Managed control plane Autoscaling Read full review 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. Read full review Cons AWSIAM integration with Kubernetes RBAC could be better. Enabling some add-ons like service mesh, and monitoring will be nice instead of having to install them yourself after the creation of the cluster. EKS bootstrap time could be faster ... Read full review 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. Read full review Support Rating No real support channel, the Mesos
GitHub issues list was the only one we found and it wasn't particularly helpful.
Read full review Alternatives Considered It feels like AWS is behind the EKS race, the only advantage I'm able to see right now is the support of IPv6, however, trying to promote AWS alternatives that are different from the market and more like a vendor locking solutions like ECS/Fargate have kept AWS behind and focusing on the wrong things. EKS needs to really improve its integration with the
Kubernetes ecosystem and have an enterprise solution for monitoring, backups, and service mesh.
Read full review 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.
Read full review Return on Investment Migrating all our workloads from ec2 VMs to containers running in Kubernetes has been a huge improvement for the management and resilience of our Infrastructure. EKS Upgrade process to a new version seems to be taking very long .... EKS creation time usually takes over 10 minutes in us-east-1, we would like faster creation times to be under 5 minutes. Read full review 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. Read full review ScreenShots