Amazon Elastic Kubernetes Service (EKS) vs. IBM Cloud Code Engine

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.

Incentivized

It would be a good solution for running serverless applications. Because infrastructure setup and maintenance expenses can be avoided, the investment will pay for itself. The time to value is short, allowing IT to respond to business demands quickly. It aided us in customizing security as well as operating a personal project using to autoscale up and down approach. Also, because there isn't much hassle, items can be pushed into production as soon as possible. Simply push a container, create an application, and you're ready to go. But, It is less suited when you have a static machine or need to keep data in some way and do not want to utilize network storage or a database.

Incentivized

• Upgrade the kubernetes clusters to the latest version with a single click
• Auto scaling policies to automatically scale the nodes
• Detailed logs and events on the cluster within the EKS clusters portal, cloudwatch logs and metrics

Incentivized

• Managed Environment for partners and customers - shifting skills and speed to CSP
• A variety of programming model support
• Elastic scalability for cloud native development and speed
• Flexible consumption model
• Containerized workloads with horizontal scalability
• Here is an example - live demo walk-thru delivered to partners and community:
• https://www.youtube.com/watch?v=MCBClYgpDFg

Incentivized

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

Incentivized

• the pricing structure is complicated, and the servers are expensive. I really think they should offer better pricing options and support for more languages
• sometimes the servers go down, and they take too long to respond to support tickets
• uploading documents is slow since I have to do it one by one, making the process much longer than it should be

Incentivized

Since this capability supports a wide variety of use cases - all on non proprietary and open technology based frameworks

Incentivized

Cluster maintanence is reduced, easier to deploy resources, great observability insights

Incentivized

Consumers can purchase individual components as well as unlocking new bundles with special features and services including the extensive data management governance capabilities of the Automation range. Kubernetes containerizing for effective service implementation and an agile, flexible multi-cloud data program help both utilization expansion and deployment to be improved by this architecture.

Incentivized

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.

Incentivized

What impresses me most about IBM Cloud Code Engine is the container workload management capability and the Cloud services and dataflow monitoring functionalities. Data security and network security control via IBM Cloud Code Engine is quite excellent and very responsive data integration functions and the first deployment is not very technical.

Incentivized

• Good performance of platform without hiccups
• Less number of people required to manage cluster
• Easier to deploy new microservices

Incentivized

• [One] positive is that we have one tool to learn (and a simple one) for all kinds of deployment. We need less people to maintain the system.
• We have saved a lot of time on trouble shooting. It's clear how it works. It's "just" kubernetes..

Incentivized