Apache Subversion vs. Redgate Flyway

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Apache Subversion
Score 7.9 out of 10
N/A
Apache Subversion is a version control option that is free to download and open source under the Apache 2.0 license.N/A
Redgate Flyway
Score 7.7 out of 10
N/A
Flyway, by Redgate, automates database deployments across teams and technologies. It is a database devops solution that is used to accelerate software delivery and ensure quality code.
$0
Pricing
Apache SubversionRedgate Flyway
Editions & Modules
No answers on this topic
Community Edition
$0
Teams Edition
$3,000
per year at least 10 schemas in production
Offerings
Pricing Offerings
Apache SubversionRedgate Flyway
Free Trial
NoNo
Free/Freemium Version
NoYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details——
More Pricing Information
Community Pulse
Apache SubversionRedgate Flyway
Top Pros
Top Cons

No answers on this topic

Best Alternatives
Apache SubversionRedgate Flyway
Small Businesses
Git
Git
Score 10.0 out of 10
DBeaver
DBeaver
Score 8.6 out of 10
Medium-sized Companies
Git
Git
Score 10.0 out of 10
DBeaver
DBeaver
Score 8.6 out of 10
Enterprises
Perforce Helix Core
Perforce Helix Core
Score 6.7 out of 10
DBeaver
DBeaver
Score 8.6 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Apache SubversionRedgate Flyway
Likelihood to Recommend
6.6
(10 ratings)
8.0
(4 ratings)
Likelihood to Renew
3.1
(2 ratings)
-
(0 ratings)
User Testimonials
Apache SubversionRedgate Flyway
Likelihood to Recommend
Apache
It's a relatively simple version control system so it works great for an individual or small team (less than 10 people). But if you have a medium to large team, especially one with members distributed over a large geographic area, or one where individuals need to be able to work "offline" without access to a central server, Apache Subversion will likely not be the best choice.
Also, if you're maintaining an open-source project where outside people will be interacting with your code repository, git is probably a better choice because it's becoming the de-facto standard these days and what most developers are familiar with.
Read full review
Redgate
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.
Read full review
Pros
Apache
  • Revision control done properly - you have end to end visibility of all changes in the project.
  • Conflict resolution - visually highlighting the differences helps to track down the problem.
  • Being open source and very popular.
  • We are using SVN hosted in our network - it is very stable, we had almost zero downtime in 4 years.
  • Rollbacks are made simple and easy to use.
Read full review
Redgate
  • Supports many databases
  • Community version uses Apache license
  • Widely used, good community support
Read full review
Cons
Apache
  • Distributed development - I've never worked in an environment where distributed development (developers widely scattered geographically) was a factor, but that's why git exists.
  • Merging - Merging of code from one branch to another can be painful, especially if it's not done frequently. (On the other hand, doing merges is one of the reasons I get a nice salary, so I can't complain too much!)
  • Acceptance - Let's face it, git is what "all the cool kids are using." If you've got a bunch of developers fresh out of school, they'll probably know git and not Subversion.
Read full review
Redgate
  • 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
Read full review
Likelihood to Renew
Apache
While there are interesting alternatives, such a GIT, Subversion has been a breath of fresh air compared to its predecessors like CVS or Microsoft Source Safe (now called Team Foundation Server). Its ease of use and high adoption rate is going to keep me using this product for years to come.
Read full review
Redgate
No answers on this topic
Alternatives Considered
Apache
Git has become the new standard of version control, with its support for distributed design. As a tool to manage and control versions, Subversion does it well, but Git is the future.
Read full review
Redgate
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.
Read full review
Return on Investment
Apache
  • Subversion helps us feel secure in maintaining access to all of our product code, both current and historical.
  • Being free and open source makes it an even better "investment".
Read full review
Redgate
  • Reduced our effort for release processes.
  • Easy to setup - less than 5 minutes.
  • Improve reliability of our databases.
  • Easy backup and version control.
Read full review
ScreenShots