Need advice about which tool to choose?Ask the StackShare community!
AWS CodeCommit vs Azure DevOps: What are the differences?
Developers describe AWS CodeCommit as "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. On the other hand, Azure DevOps is detailed as "Services for teams to share code, track work, and ship software". Azure DevOps provides unlimited private Git hosting, cloud build for continuous integration, agile planning, and release management for continuous delivery to the cloud and on-premises. Includes broad IDE support.
AWS CodeCommit belongs to "Code Collaboration & Version Control" category of the tech stack, while Azure DevOps can be primarily classified under "Integrated Development Environment Tools".
Some of the features offered by AWS CodeCommit are:
- Collaboration
- Encryption
- Access Control
On the other hand, Azure DevOps provides the following key features:
- Agile Tools: kanban boards, backlogs, scrum boards
- Reporting: dashboards, widgets, Power BI
- Git: free private repositories, pull requests
"Free private repos" is the primary reason why developers consider AWS CodeCommit over the competitors, whereas "Complete and powerful" was stated as the key factor in picking Azure DevOps.
simplement-e, Proactima Solutions AS, and Poq are some of the popular companies that use Azure DevOps, whereas AWS CodeCommit is used by iMedicare, Complete Business Online, and Sidecar Interactive. Azure DevOps has a broader approval, being mentioned in 69 company stacks & 65 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 Azure DevOps
- Complete and powerful56
- Huge extension ecosystem32
- Azure integration27
- Flexible and powerful26
- One Stop Shop For Build server, Project Mgt, CDCI26
- Everything I need. Simple and intuitive UI15
- Support Open Source13
- Integrations8
- GitHub Integration7
- One 4 all6
- Cost free for Stakeholders6
- Project Mgmt Features6
- Crap5
- Runs in the cloud5
- Agent On-Premise(Linux - Windows)3
- Aws integration2
- Link Test Cases to Stories2
- Jenkins Integration2
- GCP Integration1
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 Azure DevOps
- Still dependant on C# for agents8
- Many in devops disregard MS altogether5
- Capacity across cross functional teams not visibile4
- Not a requirements management tool4
- Half Baked4
- Jack of all trades, master of none3
- Poor Jenkins integration3
- Tedious for test plan/case creation2