Apache Subversion vs. AWS CodeArtifact

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Apache Subversion
Score 9.6 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
AWS CodeArtifact
Score 8.7 out of 10
N/A
AWS CodeArtifact is a fully managed artifact repository service that aims to make it easy for organizations of any size to securely store, publish, and share software packages used in their software development process. CodeArtifact can be configured to automatically fetch software packages and dependencies from public artifact repositories so developers have access to the latest versions.N/A
Pricing
Apache SubversionAWS CodeArtifact
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Apache SubversionAWS CodeArtifact
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Apache SubversionAWS CodeArtifact
Best Alternatives
Apache SubversionAWS CodeArtifact
Small Businesses
Git
Git
Score 10.0 out of 10
Git
Git
Score 10.0 out of 10
Medium-sized Companies
Git
Git
Score 10.0 out of 10
Git
Git
Score 10.0 out of 10
Enterprises
Perforce P4
Perforce P4
Score 7.2 out of 10
Git
Git
Score 10.0 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Apache SubversionAWS CodeArtifact
Likelihood to Recommend
6.6
(10 ratings)
8.0
(1 ratings)
Likelihood to Renew
3.1
(2 ratings)
-
(0 ratings)
User Testimonials
Apache SubversionAWS CodeArtifact
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
Amazon AWS
We have a small team with limited resources and it worked well for us. Hence I can conclude that AWS Code Artifact are well suited for organizations which have limited resources in terms of hardware and access to administrators for setting up artifact repository in-house. AWS Code Artifact is also suited particularly well for organization(s) which are already using AWS Services/Infrastructure (eg. EC2) . It works quite well with existing AWS services and completes the gap which existed in AWS offering for quite some time. Organizations can move their entire DevOps toolchain and infrastructure to Amazon. It is less appropriate for organization(s) which rely on artifacts like Debian, C/C++, Go etc as AWS does not support those fully.
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
Amazon AWS
  • Code Artifact is a cloud based artifact repository so there is no installation required.
  • Code Artifact comes with out of the box security. Using RBAC and encryption
  • Total cost of usage is less than setting up in-house servers
  • It is accessible from any where.. so no additional network setup is required.
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
Amazon AWS
  • CodeArtifact does not support packages like debian. It will be nice to see them support that.
  • Does not provide security scanning of the packages
  • Lacks support for third party CI/CD toolchain like Jenkins
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
Amazon AWS
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
Amazon AWS
AWS CodeArtifact is an excellent choice for organization(s) which are looking to move their infrastructure and devops toolchain to Amazon. It is very useful for teams/organizations on limited budget or do not want to take on infrastructure and maintenance costs associated with the artifact repository. Other software solutions require resources for setting up and need ongoing maintenance.
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
Amazon AWS
  • Overall CodeArtifact has positive ROI on the our team. We had limited budget for procurement of server/administrators. With CodeArtifact we were able to get some savings.
  • We were able to deliver faster hence customers were quite happy. That led to customer satisfaction
  • We didnt have to invest on maintaining network infrastructure/uptime and security. That saved us quite a bit of hassle and funds.
Read full review
ScreenShots