While this isn't surprising considering how bad it was, it is surprising considering that they recently announced the whole Amazon Q for software development thing. Who's going to trust them with Dev tooling now?
AWS Code Commit Ceased Onboarding New Customers
31–40 of 86 posts
Re: AWS Code Commit Ceased Onboarding New Customers
#32Earlier quoted context omitted.
>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.
Funnily enough when my infra team talked to AWS solution architects about this topic, it seems they were very upfront: don't touch CodeCommit, AWS/Amazon teams mostly use GitLab internally. And we do have a partnership plus discounts conditional to minimum usage volumes.
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.
Re: AWS Code Commit Ceased Onboarding New Customers
#33Earlier quoted context omitted.
> Their blog post about how to rewrite QLDB apps to use Aurora PostgreSQL instead Straight callback to all the "you don't need a blockchain, you just need a database".
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…
This makes me wonder if Hedera Hashgraph can support this use case...
Re: AWS Code Commit Ceased Onboarding New Customers
#34Earlier quoted context omitted.
Funnily enough when my infra team talked to AWS solution architects about this topic, it seems they were very upfront: don't touch CodeCommit, AWS/Amazon teams mostly use GitLab internally. And we do have a partnership plus discounts conditional to minimum usage volumes.
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.
Re: AWS Code Commit Ceased Onboarding New Customers
#35Not 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.
Having been on both sides, it often makes a lot of sense. A lot of companies have surprises requirements in contacts, such as HIPPA or military/classified or whatnot. The cost of adding a new vendor can be astronomical compared to the cost of dealing with CodeCommit.
In truth, though, Amazon should have bought gitlab instead.
Re: AWS Code Commit Ceased Onboarding New Customers
#36Cue rebrand to “AWS Code Freeze”.
Re: AWS Code Commit Ceased Onboarding New Customers
#37Earlier 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.
Amazon has a uniquely large spread, in that case.
I use S3, EC2, Route 53, and RDS. That's more or less it. I advise others to do likewise. Not the same set, mind you, but the same mindset.
Re: AWS Code Commit Ceased Onboarding New Customers
#38Earlier quoted context omitted.
> Their blog post about how to rewrite QLDB apps to use Aurora PostgreSQL instead Straight callback to all the "you don't need a blockchain, you just need a database".
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.
Re: AWS Code Commit Ceased Onboarding New Customers
#39Hoping they never disable cloud9 for my account
Re: AWS Code Commit Ceased Onboarding New Customers
#40AWS CodePipeline + CodeDeploy are horrors¹ from what I saw at a client.
They had mandated .Net + Javascript for all development, GitHub for versioning, and AWS for all other cloud services.
The different projects they had going were not complex or huge.
Yet it took months to get it up and running. The last month at least they paid for AWS specialists to come in and set it up and even they spent weeks.
Throughout it all, any notion of trying a different CI/CD stack were rudely dismissed.
Once it was up and running nobody dared touch the pipeline again.
From all the AWS services that the customer used nothing was ever comparable to the horrors of their CI/CD.
Setting it up with Azure's offerings would have been damned near trivial. I have however not used those in production so I do not have the experience to able to say it is a better solution over all.
¹ In fairness, AWS had just recently released the CI/CD offerings and things may be a lot better now. I havent look at it again since then.