[ChicagoDave]

I suspect there's still a lot of FUD regarding public cloud as well as on-prem admins and engineers actively pushing back for fear of losing their jobs. (I've seen this in action)

There certainly are legitimate reasons not to move to public cloud, but it shouldn't be an emotional one.

Measure cost (including manpower), SLA's, performance, governance, and compliance. After that it should be simple to stay on-prem, go hybrid, or move full force into public cloud.

I think a more complex problem is that many companies have legacy web applications that probably should be rebuilt cloud-native/serverless. Doing a lift and shift can be cost-effective, but decomposing these applications and rebuilding them in serverless would probably provide significant savings.

[vidarh]

I see more FUD the other way, about high devops costs etc. As someone who has spent years consulting both on on prem systems, dedicated hosting and AWS, I typically ended up billing more ops time to the AWS clients - they still have 90% of the same ops needs and then in addition they need to manage the AWS specific bits.

In terms of actual hosting costs, I've more than once been prepared to offer clients to move them off AWS and guarantee my fee will simply be a percentage of the savings - I've seen clients cut hosting cost between 50% and 90% on moving from AWS to dedicated hosting, and cut their devops costs at the same time.

For someone doing admin/devops who wants to maximize billable hours, recommending AWS would be better than recommending on-prem - it's all remote, no annoying travel etc., and you're likely to make more money, and at the same time you ironically gets less pressure from managers who have been told cloud will cut their costs.

> Doing a lift and shift can be cost-effective, but decomposing these applications and rebuilding them in serverless would probably provide significant savings.

Even if you rebuild them as "serverless" you'd probably end up saving far more by deploying said "serverless" apps on dedicated hosting providers for the base load.

[gaius]

as on-prem admins and engineers actively pushing back for fear of losing their jobs.

The funny thing is: those jobs already went years ago outsourced to “smart hands” in the DC. You still need people to plan and operate all this stuff. SAs who make the jump willingly have nothing to fear from cloud.

[Spooky23]

A lot of the folks in these roles have gotten lazy in legacy jobs. Lots of enterprise ops organizations are doing stuff with 10 people that could be done with 3.