Live data from Hacker News

AWS Code Commit Ceased Onboarding New Customers

repost.aws

41–50 of 86 posts

Re: AWS Code Commit Ceased Onboarding New Customers

#41
post #34
post #32

Earlier quoted context omitted.

Slight correction, the sales org uses GitLab, mainly to segregate any “code” they build for customers. Internal AWS/Amazon teams use an internal git-backed UI.

The fact that there was no dogfooding in many years here tells everything one needs to know about CodeCommit.

AWS CantCommit

Re: AWS Code Commit Ceased Onboarding New Customers

#42
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.

Well, git is kinda popular.

Re: AWS Code Commit Ceased Onboarding New Customers

#43

I once had high hopes Amazon would be able to build a real GitHub competitor. It's a real shame Amazon doesn't seem to be able to build anything that reaches beyond their walled garden.

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

User friendliness is not AWS moat. Anything that is facing a larger audience other than those that have regular access to their tooling (either cli or UI) is far from being ready for large adoption.

Re: AWS Code Commit Ceased Onboarding New Customers

#45
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…

>be used by those teams who want to move as much as possible to AWS By teams that have been mandated to move as much as possible to AWS by their company's senior leadership, because it simplified accounts/they negotiated a "great contract" etc.

Software devs fall to hype sometimes. It's not just management. But I guess it's easier to always look for blame elsewhere.

Re: AWS Code Commit Ceased Onboarding New Customers

#46
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…

Oh, you, thanks for your blog posts, had several in my newsletter so I recognized your name. Thanks again.

Re: AWS Code Commit Ceased Onboarding New Customers

#49
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.

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.

Re: AWS Code Commit Ceased Onboarding New Customers

#50
post #49
post #38

Earlier quoted context omitted.

> 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.

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.

Most people? There is a Django-history module, and yet it’s not nearly as popular as Django. I’ve used this on two out of 100 projects. No one ever actually wanted the history, it’s there for “just in case of an audit” and compliance, which never comes.
Post reply on HN