Amazon Elastic Kubernetes Service (EKS) vs. Redgate Flyway

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

Database Migrations on Java-based solutions. It has one of the best integrations with it as a database migration tool, you can do it with the community edition (no pricing involved) and it works flawlessly with Maven and Gradle. It's not an expensive tool in order to use the next level of features and is worth the money. I would recommend reaching that edition level as the object mapping feature gets really handy. I would not recommend it for any Microsoft-based solution (.Net) as is not compatible at all based on my experience, this is a tool only worth it with Java applications.

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

• Supports many databases
• Community version uses Apache license
• Widely used, good community support

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

• GUI could be more user friendly
• Applying patch scripts on a blank DB differs from on a DB with data, so the migration could still fail when all tests passed
• Configurations options could be more flexible / powerful

Incentivized

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

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

The problem with a cloud-based tool for migration services is the cloud dependency. You are restricted to use the tool along the Cloud provider. Flyway gives you the freedom to use it in any scenario as long as you are working with a compatible database engine. Even if you are working on-premise and you don't have plans to move to a cloud architecture. Or even for sandbox development scenarios where you are a developer playing around with some project ideas. And you don't have to pay anything as long as you need advanced features, and not less importantly, you are using an open-source tool.

Incentivized

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

Incentivized

• Reduced our effort for release processes.
• Easy to setup - less than 5 minutes.
• Improve reliability of our databases.
• Easy backup and version control.

Incentivized