Need advice about which tool to choose?Ask the StackShare community!
AWS CodeCommit vs SVN (Subversion): What are the differences?
AWS CodeCommit: Fully-managed source control service that makes it easy for companies to host secure and highly scalable private Git repositories. CodeCommit eliminates the need to operate your own source control system or worry about scaling its infrastructure. You can use CodeCommit to securely store anything from source code to binaries, and it works seamlessly with your existing Git tools; SVN (Subversion): Enterprise-class centralized version control for the masses. Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations.
AWS CodeCommit can be classified as a tool in the "Code Collaboration & Version Control" category, while SVN (Subversion) is grouped under "Version Control System".
"Free private repos" is the primary reason why developers consider AWS CodeCommit over the competitors, whereas "Easy to use" was stated as the key factor in picking SVN (Subversion).
SVN (Subversion) is an open source tool with 326 GitHub stars and 118 GitHub forks. Here's a link to SVN (Subversion)'s open source repository on GitHub.
Coderus, Performance Assessment Network (PAN), and Die Coder GmbH are some of the popular companies that use SVN (Subversion), whereas AWS CodeCommit is used by iMedicare, Complete Business Online, and Sidecar Interactive. SVN (Subversion) has a broader approval, being mentioned in 77 company stacks & 58 developers stacks; compared to AWS CodeCommit, which is listed in 24 company stacks and 17 developer stacks.
Pros of AWS CodeCommit
- Free private repos44
- IAM integration26
- Pay-As-You-Go Pricing24
- Amazon feels the most Secure20
- Repo data encrypted at rest19
- Faster deployments when using other AWS services11
- I can make repository by myself if I have AWS account11
- AWS CodePipeline integration8
- Codebuild integration6
- Does not support web hooks yet! :(6
- Cost Effective4
- No Git LFS! Dealbreaker for me2
- Integrated with AWS Ecosystem2
- Elastic Beanstalk Integration2
- Integration via SQS/SNS for events (replaces webhooks)1
- IAM1
- Open source friendly1
- Only US Region1
- Available in Ireland (Dublin) region1
- CodeDeploy Integration1
- Issue tracker1
- CodeCommit Trigger for an AWS Lambda Function1
- Ui0
Pros of SVN (Subversion)
- Easy to use20
- Simple code versioning13
- User/Access Management5
- Complicated code versionioning by Subversion3
- Free2
Sign up to add or upvote prosMake informed product decisions
Cons of AWS CodeCommit
- UI sucks12
- SLOW4
- No Issue Tracker3
- Bad diffing/no blame2
- NO LFS support2
- No fork2
- No webhooks2
- Can't download file from UI1
- Only time based triggers1
- Accident-prone UI0
Cons of SVN (Subversion)
- Branching and tagging use tons of disk space7
Sign up to add or upvote consMake informed product decisions
What is AWS CodeCommit?
What is SVN (Subversion)?
Need advice about which tool to choose?Ask the StackShare community!
What companies use SVN (Subversion)?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with AWS CodeCommit?
What tools integrate with SVN (Subversion)?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+7