Azure Kubernetes Service (AKS) vs. Redgate Flyway

AKS works very well for running containerized applications that require high availability and scalability. This includes systems like our HRIS platform and customer-facing web applications. AKS is a good choice when applications are broken into multiple services that need independent scaling and deployment. It provides the flexibility needed to manage these architectures effectively. But for single, low-traffic applications or simple internal tools, AKS can be overkill. For scenarios like that Azure App Service would be better.

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

• AKS makes it easier to replicate data to multiple regions
• Azure portal make it easier to manage the resources of the organization

Incentivized

• Manage DB migration patch scripts
• Apply DB migration patch scripts
• Test DB migration patch scripts
• Setup new DB instances, including on local env

Incentivized

• Steep learning curve
• Expected charges are unclear until you see real production usage
• Operations teams need to learn an entirely new skill set

Incentivized

• Updating it causes problems, there have been unnecessary changes that wasted time
• Requires knowledge & studying so it's used properly
• Lots of options that might be difficult to understand for non technical people

Incentivized

As already said, the UI/CLI and even terraform are perfectly fine, but certain details could be documented better. For instance, if I want to secure the whole Azure Kubernetes Service (AKS) with my own managed keys, then it is very complex and hard to get there. Not really a single source that gives you the whole picture. Besides that, it is still good to use, in most cases intuitive but details mentioned as above can be tricky.

Incentivized

It's very easy to install and use. Even someone very new to the software will have no trouble, plus the team reach out to help you and continue to offer you support throughout. Really simple interface, clean design, all you could really ask for in a tool that needs to do a job dependably

Incentivized

Microsoft support was really good, whenever we raise any ticket they come back to us within a couple of hours.

Incentivized

Amazon EKS stacked up very well and had better performance in some areas. However, Azure Kubernetes Service was a better fit given our Azure environment.

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

• We had to spend more time on Azure Kubernetes Service (AKS) than on AWS and GCP to get our kubernetes cluster up and running
• The resources on nodes need to be left out unused, so effectively it is wasting money there
• It definitely made us spend more time into maintaining kubernetes

Incentivized

• I definitely think it do have positive impact to our company's database management.
• We have 4 database environments and thus it is easy when we push the database to various environments.