Live data from Hacker News

AWS will discontinue support for AWS App Mesh

aws.amazon.com

31–37 of 37 posts

Re: AWS will discontinue support for AWS App Mesh

#31

Earlier quoted context omitted.

explaining that KTLO requires 6 SDEs is something I wish every executive knew.

are we assuming only 9-5? 2.3 SDE could do that, but i don't get 6. a 24/7 operation needs 2FTE and 1 PTE per shift, and there are three shifts. And i suppose "6 SDEs" for a service that has... what number of MAU or whatever? me and a great friend of mine split our roles with our "projects", he deals with paid clients, and i deal with our required services (email, matrix, nextcloud, pastebins, misskey, PBXen, wiregua…

> 2.3 SDE could do that, but i don't get 6. a 24/7 operation needs 2FTE and 1 PTE per shift, and there are three shifts.

having the team constantly on call is a recipe for having them quit. sure, you could run this with the bare minimum number of engineers, but your turnover would be so high and given how high hiring costs tend to be, this is a net negative

> so maybe all that "busywork" takes 6 full times?

ktlo in a constantly changing company is not easy. software / host patching to maintain compliance is necessary busywork that requires a bit of babysitting. not to mention keeping up with required migrations to new stuff due to internal deprecations.

Re: AWS will discontinue support for AWS App Mesh

#32
post #23
post #19

Earlier quoted context omitted.

> But if you are using a (costly) managed service it's because you don't want the hurdle of managing the service. On the other hand part of the trade offs of using such services is that you have no control of when they will become unavailable. Its not just normal, its expected.

I doubt very many businesses have anything but a surface level "vaguely gestures toward Azure maybe" plan for if EC2 ever shuts down.

I don’t have a plan for what happens if TCP goes away either, but that also seems fine.

EC2 and S3 are backbone/foundational enough that I expect they’ll be running the last year that AWS exists.

Re: AWS will discontinue support for AWS App Mesh

#33
post #22

Earlier quoted context omitted.

Cognito feels like its bones are grinding together

They can’t really get rid of Cognito. It’s the authentication/authorization platform for external users. There is no migration path that will seamlessly transfer user names and passwords to other mainstream services like CodeCommit.

I can see reduced federation options and increased costs, but Cognito is OAuth so it's never going to die. You might as well try to get rid of IAM.

Re: AWS will discontinue support for AWS App Mesh

#34
post #9
post #2

A company with Amazons resources could keep these fringe services around as long as there are paying customers. Just increase the price of the service to match the costs of keeping the legacy service around.

Three problems with this approach. 1. The ongoing “ktlo” (keep the lights on) maintenance cost for a minimal public aws service is on the order of 6 SDEs. Theres a constant stream of security and integration improvements like new IAM policy features, KMS handling, billing & metering, console chrome, docs, etc. These are generally nonnegotiable to keep _any_ sort of consistency across AWS. This is discounting most ope…

You’re forgetting one important point. No one who has any interest in their career inside or outside of Amazon wants to be on a service team for a dead service. That would look horrible on both their promo doc internally and when trying to get through a behavioral interview externally.

Source: former AWS employee

Re: AWS will discontinue support for AWS App Mesh

#35
post #4
post #2

A company with Amazons resources could keep these fringe services around as long as there are paying customers. Just increase the price of the service to match the costs of keeping the legacy service around.

From all what I've heard over the years, they have a problem staffing the service teams. I imagine with the AI craze that just got worse, as they certainly shifted resources to work on that. If they really have staffing problems, it'd make sense in the short-term to shut down services which don't bring in much revenue. In the long-term that might fire back if AWS customers loose trust in the services they're using st…

> In the long-term that might fire back if AWS customers loose trust in the services they're using still being there in the future.

Where are they going to go to get higher guarantees of services not being abandoned? Google?

> The obvious solution to a possible staffing problem would of course be not fire a certain percentage of your employees every year.

Have you worked for a BigTech company and seen their promo doc? No developer would want to work on a dead end service who was interested in their career.

Re: AWS will discontinue support for AWS App Mesh

#36
post #4
post #2

A company with Amazons resources could keep these fringe services around as long as there are paying customers. Just increase the price of the service to match the costs of keeping the legacy service around.

From all what I've heard over the years, they have a problem staffing the service teams. I imagine with the AI craze that just got worse, as they certainly shifted resources to work on that. If they really have staffing problems, it'd make sense in the short-term to shut down services which don't bring in much revenue. In the long-term that might fire back if AWS customers loose trust in the services they're using st…

Really? I've heard Amazon is so understanding of the difficulty in new hires picking up legacy code, even with the extremely diligent help of the other "mates" on their "team".

I'm sure with the excellent work life balance, supportive atmosphere, nurturing organization, and upbeat attitude, Amazon's staffing issues are just a short blip.

One thing Amazon is known for us a good place for a long term stable career!

It's a good thing that organizations employment is so stable with so many foundational services that so much of our economy depends upon.

Re: AWS will discontinue support for AWS App Mesh

#37

The one service that is not dead yet. But is smelling funny is CodePipeline. It is so bad and they’ve already discontinued CodeCommit (the very bad hosted git service), Cloud9 (hosted IDE that is based on VSCode even though they would never admit it externally) and CodeStar.

A couple comments:

AFAIK cloud9 was never vscode based, it was a dutch startup acquisition when hosted RDEs were looking popular https://siliconcanals.com/amazon-acquires-cloud9/. I believe theyre busy working on similar-but-not-obviously related remote environments like AWS Workspaces.

Re: existing Code-asterisk _services_ see CodeCatalyst at a recent (in progress) attempt to move to a more unified user-centric _product_.

And for downthread Cognito, Id be surprised if it ever goes away. i think theres some unification/deconfliction of capabilities that needs to happen with Federate. But Id expect one or both of those to stick around as a proxy pool of user identities for apps. The more interesting, and huge change to how AWS fundamentally works, is Identity Center(IdC). Tying back to cognito and CodeCatalyst IdC should _finally_ bring user identities, and your corp IdP, in to AWS and actually be useful across existing services. This _could_ catch AWS up to goog cloud and OCI and (I assume) azure on identity management.

Edit: ex AWS, but all if the above based on publicly available information.

Post reply on HN