AWS CodeCommit vs. Mercurial

Non-cloud users often complain about CodeCommit because it is so barebones, which it is. However, I believe that is by design. It is not supposed to be a full-fledged AI integrated GitLab alternative. Once users or developers get over the learning curve and required Cloud dependency, CodeCommit is a great service that offers a perfect complement / augmentation to on prem options. It is ideal for Cloud-native deployments where the code and production service are close together.

If you generally think that to develop software you have to choose one repository, then in my opinion you have to choose between Mercurial and Git, there is not other solution. Mercurial also has a good merge tool which i can recommend. This gives you the flexibility to push just the "part of the feature", and is much better suited in the case where the "part of feature" and some other "part of the feature" both contain changes to the same file.

Incentivized

• Lightweight
• Native IAM integration
• Collaboration
• High Availability

• Branch
• Distributed architecture
• Stable
• Platform independent

Incentivized

• Integration with non-Cloud services
• Learning curve for devs
• Barebones

• Integration with visual studio
• More integrated tools
• When I install Mercurial I always have to do a hard restart of my computer.

Incentivized

CodeCommit is a cloud native solution where GitHub is typically run on prem which requires a team to manage the physical servers and the software on top of it. CodeCommit is a better choice when doing Cloud focused workloads. GitHub Copilot offers more features than the leaner CodeCommit, however does not have the same integration options

When we chose Mercurial it was more popular from perspectives than Git and we have too many problems with the Microsoft team foundation solution. We also want to move from a centralized version of source control to a distributed one. We also were working more and more via the Internet with our source control so distributed version was only solution.

Incentivized

• 20% reduction in traffic to on-prem GitHub
• No additional server capacity required
• No overhead or maintainance

• Improve time in merging
• Branching enables us to keep separate version per customer
• Good tool for programmers is sometimes a reason to stay

Incentivized