Need advice about which tool to choose?Ask the StackShare community!

AWS CodeCommit

327
824
+ 1
193
Azure DevOps

2.7K
2.8K
+ 1
248
Add tool

AWS CodeCommit vs Visual Studio Team Services: What are the differences?

Key Differences between AWS CodeCommit and Visual Studio Team Services

AWS CodeCommit and Visual Studio Team Services (VSTS) are two popular tools used by developers for version control and collaboration. While both tools offer similar functionalities, there are several key differences between them.

1. Integration with other AWS services: AWS CodeCommit is seamlessly integrated with other AWS services such as AWS CodeBuild and AWS CodePipeline, providing a complete CI/CD (Continuous Integration/Continuous Deployment) pipeline. On the other hand, VSTS offers integrations with a wider range of tools and platforms, including Azure, GitHub, and Jenkins, making it a more versatile choice for organizations working with diverse technologies.

2. Hosting options: AWS CodeCommit is a fully managed service that is hosted entirely within the Amazon Web Services (AWS) cloud. This eliminates the need for organizations to manage their own infrastructure for version control. In contrast, VSTS offers both cloud-hosted and self-hosted options, allowing organizations to choose whether to keep their repositories on a third-party cloud or behind their own firewall, depending on their security and compliance requirements.

3. Pricing model: The pricing models for AWS CodeCommit and VSTS differ significantly. AWS CodeCommit is primarily priced based on the number of active users and the amount of data stored, making it a cost-effective choice for smaller teams or projects. VSTS, on the other hand, has a more complex pricing structure that includes options for different user licenses, build and release pipelines, and additional features such as package management. This makes it more suitable for larger organizations with complex requirements.

4. User interface and user experience: VSTS provides a user-friendly and intuitive interface, with a visual representation of code branches and pull requests. It also offers features such as customizable dashboards and built-in reporting and analytics, providing greater visibility and insights into the development process. AWS CodeCommit, while functional, has a simpler interface with fewer bells and whistles, which may be preferred by users who value simplicity and minimalism.

5. Security and compliance: AWS CodeCommit offers strong security features, including encryption at rest and in transit, granular access controls, and integration with AWS Identity and Access Management (IAM) for user authentication and authorization. It also complies with various industry standards and regulations, such as ISO and SOC. VSTS also provides similar security features, but the level of control and compliance may vary depending on the hosting option chosen.

6. Ecosystem and community support: VSTS has a larger ecosystem and a more active community compared to AWS CodeCommit. This means that developers using VSTS can benefit from a wider range of third-party integrations, plugins, and community-driven resources such as forums and tutorials. AWS CodeCommit, being a relatively newer service, may have a smaller ecosystem and community support.

In Summary, AWS CodeCommit and VSTS differ in terms of integration with other AWS services, hosting options, pricing model, user interface and user experience, security and compliance features, and ecosystem/community support. The choice between the two tools depends on the specific needs and preferences of the organization or development team.

Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of AWS CodeCommit
Pros of Azure DevOps
  • 44
    Free private repos
  • 26
    IAM integration
  • 24
    Pay-As-You-Go Pricing
  • 20
    Amazon feels the most Secure
  • 19
    Repo data encrypted at rest
  • 11
    Faster deployments when using other AWS services
  • 11
    I can make repository by myself if I have AWS account
  • 8
    AWS CodePipeline integration
  • 6
    Codebuild integration
  • 6
    Does not support web hooks yet! :(
  • 4
    Cost Effective
  • 2
    No Git LFS! Dealbreaker for me
  • 2
    Integrated with AWS Ecosystem
  • 2
    Elastic Beanstalk Integration
  • 1
    Integration via SQS/SNS for events (replaces webhooks)
  • 1
    IAM
  • 1
    Open source friendly
  • 1
    Only US Region
  • 1
    Available in Ireland (Dublin) region
  • 1
    CodeDeploy Integration
  • 1
    Issue tracker
  • 1
    CodeCommit Trigger for an AWS Lambda Function
  • 0
    Ui
  • 56
    Complete and powerful
  • 32
    Huge extension ecosystem
  • 27
    Azure integration
  • 26
    Flexible and powerful
  • 26
    One Stop Shop For Build server, Project Mgt, CDCI
  • 15
    Everything I need. Simple and intuitive UI
  • 13
    Support Open Source
  • 8
    Integrations
  • 7
    GitHub Integration
  • 6
    One 4 all
  • 6
    Cost free for Stakeholders
  • 6
    Project Mgmt Features
  • 5
    Crap
  • 5
    Runs in the cloud
  • 3
    Agent On-Premise(Linux - Windows)
  • 2
    Aws integration
  • 2
    Link Test Cases to Stories
  • 2
    Jenkins Integration
  • 1
    GCP Integration

Sign up to add or upvote prosMake informed product decisions

Cons of AWS CodeCommit
Cons of Azure DevOps
  • 12
    UI sucks
  • 4
    SLOW
  • 3
    No Issue Tracker
  • 2
    Bad diffing/no blame
  • 2
    NO LFS support
  • 2
    No fork
  • 2
    No webhooks
  • 1
    Can't download file from UI
  • 1
    Only time based triggers
  • 0
    Accident-prone UI
  • 8
    Still dependant on C# for agents
  • 5
    Many in devops disregard MS altogether
  • 4
    Capacity across cross functional teams not visibile
  • 4
    Not a requirements management tool
  • 4
    Half Baked
  • 3
    Jack of all trades, master of none
  • 3
    Poor Jenkins integration
  • 2
    Tedious for test plan/case creation

Sign up to add or upvote consMake informed product decisions

What is AWS CodeCommit?

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.

What is Azure DevOps?

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.

Need advice about which tool to choose?Ask the StackShare community!

What companies use AWS CodeCommit?
What companies use Azure DevOps?
See which teams inside your own company are using AWS CodeCommit or Azure DevOps.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with AWS CodeCommit?
What tools integrate with Azure DevOps?

Sign up to get full access to all the tool integrationsMake informed product decisions

What are some alternatives to AWS CodeCommit and Azure DevOps?
GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together.
GitLab
GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers.
Bitbucket
Bitbucket gives teams one place to plan projects, collaborate on code, test and deploy, all with free private Git repositories. Teams choose Bitbucket because it has a superior Jira integration, built-in CI/CD, & is free for up to 5 users.
GitHub Enterprise
GitHub Enterprise lets developers use the tools they love across the development process with support for popular IDEs, continuous integration tools, and hundreds of third party apps and services.
SVN (Subversion)
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.
See all alternatives