AWS staff spending ‘much of their time ’optimizing customers' clouds'

Re:AWS staff spending ‘much of their time ’optimizing custom... by jamsauceismad on Monday April 17, 2023 @02:30PM (#35604600)

It's because you did the heavy lifting up front with how your application is designed and how your infra is provisioned (I'm guessing everything is terraformed or something?).

[ Parent | on HN ]

Re:AWS staff spending ‘much of their time ’optimizing custom... by sleepybrett on Monday April 17, 2023 @02:39PM (#35604706)

Also a great unlock if you do the bulk of your work in kubernetes. Amazon is certainly doing some things in their kube implementation that will make moving suck more (karpenter, some of their other integrations) in an effort to be better and thus sticky... But it's still pretty easy to go from one kube cluster to another.

[ Parent | on HN ]

Re:AWS staff spending ‘much of their time ’optimizing custom... by vidarh on Monday April 17, 2023 @03:35PM (#35605434)

Everything in Docker containers + a service discovery layer (Consul on that particular case) will get you most of the way there as long as you don't get seduced into relying on cloud specific services.

[ Parent | on HN ]

Re:AWS staff spending ‘much of their time ’optimizing custom... by scarface74 on Monday April 17, 2023 @03:41PM (#35605514)

And then you’re managing Consul clusters (been there done that).

[ Parent | on HN ]

Re:AWS staff spending ‘much of their time ’optimizing custom... by vidarh on Tuesday April 18, 2023 @03:04AM (#35610859)

I never found that a problem. Consul was robust when I used it.

[ Parent | on HN ]