Live data from Hacker News

AWS Code Commit Ceased Onboarding New Customers

repost.aws

61–70 of 86 posts

Re: AWS Code Commit Ceased Onboarding New Customers

#61
post #54
post #49

Earlier quoted context omitted.

Eh, most people would like their apps to provide them with a browsable history of their data, and why the changes happened. It's just increases scope x100 to get anything done, so few do it... but if the tooling was available, almost all stateful applications would benefit from it.

lol no. And the DB isn’t going to tell you who what why without you writing code to support that audit in which case… that special database has solved exactly 0 problems that a traditional RDBMS already solves.

I was addressing the point "nobody wants that". And I disagreed, because: if it existed, almost everyone would want it.

The tooling just doesn't exist. Doing it with half-assed tooling increases the scope of literally every development you'd be doing, so nobody bothers with it. Ive never worked with this particular database, so no idea how it would work in practice here.

Re: AWS Code Commit Ceased Onboarding New Customers

#62
Very disappointing. CodeCommit had value in its APIs for managing and accessing Git repositories programmatically e.g. from Lambda functions. I've used it to implement simple, Git-compatible version control in some projects by calling the PutFile API. Now it will be much more complicated to achieve something similar.

Re: AWS Code Commit Ceased Onboarding New Customers

#64
post #15

In writing this up - https://simonwillison.net/2024/Jul/30/aws-codecommit-quietly... - I found out about a much more significant deprecation: Amazon QLDB (Quantum Ledger Database - a blockchain-ish thing they launched in GA in 2019) is being hard-deprecated too! They're shutting it down completely on 31st July 2025, having announced the shutdown a few weeks ago (on July 18th). QLDB shutdown announcement in the releas…

Did anyone notice it is being cancelled?

There's a Reddit thread with 38 comments, I couldn't find much else https://www.reddit.com/r/aws/comments/1e6nmy5/goodbye_amazon...

Re: AWS Code Commit Ceased Onboarding New Customers

#65
post #38

Earlier quoted context omitted.

It wasn't a blockchain per se. It basically was Amazon's Version of Rich Hickey's Datomic and them pointing people to Aurora for Migration is a bit of a joke. It's a completely different product. QLDB is an immutable database with allowing you to move back and forward in history and do live streaming of events etc with cryptographic verification built in. You _can_ set up Postgres like this but it's a lot of hoops an…

> QLDB is an immutable database with allowing you to move back and forward in history and do live streaming of events etc with cryptographic verification built in. Which no one ever needed.

I used it for a subset of the features. Financial auditing and risk rating of destination banks for a particular network.

Having an immutable database that was able to track fraud ratings, along with when exactly it occurred with the data available at the time was pretty cool. You could probably do it with other tools, but having it all in one product was nice.

The cryptographic verification was helpful for legal defence. I can't think of any other uses so we may have been their only customers.

Re: AWS Code Commit Ceased Onboarding New Customers

#66
post #19

Earlier quoted context omitted.

Doesn't it reflect more on the quality of the people involved? These tools came out at the same time as a bunch of other AWS tools that are still used. The platform itself, the company around these teams was the same, so why did Code Commit suck but other AWS products from the same vintage turned out great?

You’ve never been part of a large organization have you? I have a little insight on how things like CodeCommit fall behind the competition. I worked at AWS in the Professional Services division. For a little over two years I was on a makeshift team maintaining and improving a very popular open source project in its niche. The project was hosted on “AWS Samples” ( https://github.com/aws-samples ). Once approved for th…

When I mean the people involved I didn't mean mostly the software engineers, like you show they probably have the least contribution to the success of these projects. But the point stands that the products have to exist in the same level of bureocracy and disfunctional leadership, so someone must've been better at dealing with that in the successful products. I definitely had really good experiences as a user of several of AWS's things from the same time. Maybe it's more on product leadership but I was just musing about it. To your original question I haven't worked on such big corporations no, max size I've experienced is ~2k people for ~6 months, other than that 10-400 - so I can see how it's also a different beast.

Re: AWS Code Commit Ceased Onboarding New Customers

#67
post #24

Earlier quoted context omitted.

Hope unjustified. AWS can build low level solutions -- EC2, EBS, S3. High level stuff is garbage.

Everyone's and I mean everyone's high level stuff is garbage. Remember when Lotus Notes was the peak. The only thing constant is change etc.

GitHub is good, yes? And Excel? And Notion? And Datadog?

Lots of companies with excellent user friendly products.

GCP is good in that regard too, minus IAM.

Re: AWS Code Commit Ceased Onboarding New Customers

#68
post #66

Earlier quoted context omitted.

You’ve never been part of a large organization have you? I have a little insight on how things like CodeCommit fall behind the competition. I worked at AWS in the Professional Services division. For a little over two years I was on a makeshift team maintaining and improving a very popular open source project in its niche. The project was hosted on “AWS Samples” ( https://github.com/aws-samples ). Once approved for th…

When I mean the people involved I didn't mean mostly the software engineers, like you show they probably have the least contribution to the success of these projects. But the point stands that the products have to exist in the same level of bureocracy and disfunctional leadership, so someone must've been better at dealing with that in the successful products. I definitely had really good experiences as a user of seve…

Bezos was well known for focusing on things that “make the beer taste better”. It didn’t give AWS a competitive advantage or any real revenue by trying to host a git repository.

For years they have been making sure that their other services like CodeBuild and CodePipeline work with other hosted git providers.

Uncharacteristically, they even support creating third party git repositories with CloudFormation

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGui...

As far as working for large companies, I would rather get a daily anal probe with a cactus than ever work for a large company/“FAANG” again. I’ve repeatedly ignored overtures from Google (GCP), Microsoft (Azure) and even Oracle (OCP).

My BigTech story:

https://news.ycombinator.com/item?id=38474212

Re: AWS Code Commit Ceased Onboarding New Customers

#69

Every AWS feature requires some stupid aws cli call that gives you 12 hours of usage. So every day depending on how many products you're using, you have stupid shit to run. Was codecommit like that

No. You could either set it up with SSH or HTTPS credentials (managed via IAM Console or CLI) or use the AWS CLI's credential helper that managed everything automatically. The credential helper was a little weird to set up the first time I used it, but once I wrote up the instructions it was easy enough.

Honestly I've never come across the '12 hours of usage' thing for AWS. But I only use CodeCommit, EC2, S3, SNS, SES, and other low-level services.

Re: AWS Code Commit Ceased Onboarding New Customers

#70
post #19
post #16

Not surprised. CodeCommit was released alongside a stable of other mediocre tools for CI/CD (CodePipeline and CodeDeploy if I recall correctly) that reflected the pinnacle of AWS's mid-to-late 2010s attitude, which is to find something popular and offer an incredibly mediocre alternative to it that will still be used by those teams who want to move as much as possible to AWS. Seems like that stalled out a bit, mostly…

Doesn't it reflect more on the quality of the people involved? These tools came out at the same time as a bunch of other AWS tools that are still used. The platform itself, the company around these teams was the same, so why did Code Commit suck but other AWS products from the same vintage turned out great?

[deleted]
Post reply on HN