AWS CodeCommit vs Google Cloud Source Repositories

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

AWS CodeCommit

326
820
+ 1
193
Google Cloud Source Repositories

92
160
+ 1
0
Add tool

AWS CodeCommit vs Google Cloud Source Repositories: What are the differences?

Key Differences between AWS CodeCommit and Google Cloud Source Repositories

AWS CodeCommit and Google Cloud Source Repositories are both version control services that provide managed Git repositories for developers to securely store and manage their code. However, there are several key differences between these two services.

  1. Hosting platform: AWS CodeCommit is a service provided by Amazon Web Services (AWS), while Google Cloud Source Repositories is a service provided by Google Cloud Platform (GCP). This means that CodeCommit is hosted on AWS infrastructure, while Source Repositories is hosted on GCP infrastructure.

  2. Integration with other services: CodeCommit integrates seamlessly with other AWS services, such as AWS CodePipeline for continuous delivery and AWS CodeBuild for building and testing code. On the other hand, Source Repositories integrates with other GCP services, such as Google Cloud Functions for serverless computing and Google Cloud Build for building, testing, and deploying code.

  3. Pricing model: CodeCommit offers a pay-as-you-go pricing model, where you only pay for the resources you use. It also includes a free tier for the first five active users per month. Source Repositories, on the other hand, offers a different pricing model based on storage and data transfer, and it also includes a free tier for a certain amount of storage and commits per month.

  4. Access control: CodeCommit provides fine-grained access control through AWS Identity and Access Management (IAM), allowing you to set granular permissions for users and groups. Source Repositories, on the other hand, uses Google Cloud IAM for access control, which also provides fine-grained permissions based on roles and access levels.

  5. Code review capabilities: CodeCommit offers built-in code review capabilities, allowing developers to collaborate and review code changes before merging them into the main branch. Source Repositories, on the other hand, does not have built-in code review capabilities, but it can integrate with external code review tools like Gerrit for code review workflows.

  6. Geographical availability: CodeCommit is available in multiple AWS regions globally, allowing you to choose the region that is closest to your users and provides the lowest latency. Source Repositories, on the other hand, is available in fewer regions compared to CodeCommit, as it is limited to the regions where GCP services are available.

In summary, AWS CodeCommit and Google Cloud Source Repositories differ in terms of hosting platform, integration with other services, pricing model, access control, code review capabilities, and geographical availability.

Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of AWS CodeCommit
Pros of Google Cloud Source Repositories
  • 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
    Be the first to leave a pro

    Sign up to add or upvote prosMake informed product decisions

    Cons of AWS CodeCommit
    Cons of Google Cloud Source Repositories
    • 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
      Be the first to leave a con

      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 Google Cloud Source Repositories?

      Collaborate easily and securely manage your code on a fully featured, scalable, private Git repository. Extend your Git workflow by connecting to other GCP tools, including Cloud Build, App Engine, Stackdriver, and Cloud Pub/Sub. Get access to fast, indexed powerful code search across all your owned repositories to save time.

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

      What companies use AWS CodeCommit?
      What companies use Google Cloud Source Repositories?
      See which teams inside your own company are using AWS CodeCommit or Google Cloud Source Repositories.
      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 Google Cloud Source Repositories?

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

      What are some alternatives to AWS CodeCommit and Google Cloud Source Repositories?
      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