Remix.run Logo
rr808 8 hours ago

Still having your own hardware seems so much cheaper. Maybe even just for dev/uat environments?

Every big corporate I have worked at has lower cost of capital than Amazon, and yet they want to move to AWS. I just dont understand it.

hrmtst93837 an hour ago | parent | next [-]

I think lower cost of capital is a narrow metric and rarely reflects the real total cost of ownership once you account for ops headcount, provisioning lag, redundancy requirements, patching, and developer time.

Cloud looks expensive on sticker price, but it buys instant provisioning, autoscaling, managed databases and multi-region DR, and those benefits only pay off if you actually exploit autoscaling, reserved or savings plans, spot fleets and cost tooling like Kubecost or AWS Compute Optimizer to enforce right-sizing and kill zombie instances.

If you want cheap dev and UAT keep them on on-prem metal or cheap colo, but automate with Terraform and run reproducible runtimes like k3s or devcontainers so environments stay consistent and you do not trade lower capex for a creeping operations nightmare.

dabinat an hour ago | parent | prev | next [-]

I think it can make sense for user-facing services. I host my web and database servers with AWS because unmanaged DBs can be a PITA, Amazon is peered with basically everyone, AWS is way more generous with network speeds than many dedicated / colo providers, and it’s easy to scale capacity up and down. Backend servers are hosted with cheaper providers though.

PaulKeeble 7 hours ago | parent | prev | next [-]

The main thrust of the economic argument has been on the cost of system adminstrators that maintain the hardware. Electricity and cooling being big ongoing costs, but also when AWS released it wasn't uncommon to order a server and have it take 3 months to arrive.

I think in practice the system administrators are still in the company now as AWS engineers, they still keep all that platform stuff running and your paying AWS for their engineers too as well as electricity. It has the advantage of being very quick to spin up another box, but also machines these days can come with 288 cores, its not a big stretch to maintain sufficient surplass and the tools to allow teams to self service.

Things are in a different place to when AWS first released, AWS ought to be charging a lot less for the compute, memory and storage, their business is wildly profitable at current rates because per core machines got cheaper.

ibejoeb 7 hours ago | parent | prev | next [-]

I've moved two clients to colo. Dramatic cost savings. So many systems only use VMs and a few basic cloud features. Everyone knows this, but just to make the point, you can still use certain cloud products (cloud storage for example) just fine while running your primary workloads on your own hardware. Sometimes it makes perfect sense, and you just need someone to nudge you and tell you it's going to be ok.

bmd1905 3 hours ago | parent [-]

ou're spot on—the performance-per-dollar variance across instance families right now is wild, and static provisioning almost always leaves money on the table. The real challenge is that workload profiles shift faster than teams can manually re-evaluate these benchmarks. We actually built CloudThinker to automate exactly this: continuously mapping real-time resource usage to the most cost-efficient compute across multi-cloud environments. It's much easier when an AI agent handles the rightsizing migrations autonomously.

dkechag 8 hours ago | parent | prev | next [-]

Going to the cloud can't possibly be as cheap as owning your own hardware for obvious reasons - they have to make money somehow. Well, unless you use spot instances, which uses spare nodes. In any case, you move to the cloud despite the cost if you need the multi-region redundancy, the management/features etc. More commonly it's because the higher ups heard everybody's doing it, but oh well :D

doener 8 hours ago | parent | prev | next [-]

There are so many articles like these:

"We Moved from AWS to Hetzner. Cut Costs 89%. Here’s the Catch."

https://medium.com/lets-code-future/we-moved-from-aws-to-het...

selectively 8 hours ago | parent [-]

You just linked AI slop.

doener 8 hours ago | parent [-]

You mean the image? The text does not sound like AI at all IMHO.

dkechag 7 hours ago | parent [-]

> No theory. No fluff. Just production.

ChatGPT tells me "no theory, no fluff" all the time :D

BeastMachine 4 hours ago | parent [-]

Where do you think it learned that phrasing from?

deaux 3 hours ago | parent [-]

Not from people using that same phrasing twice within a few sentences.

""" No warning. No traffic spike. Just… more money gone.

That’s when I finally looked at Hetzner.

I’ve seen too many backend systems fail for the same reasons — and too many teams learn the hard way.

So I turned those incidents into a practical field manual: real failures, root causes, fixes, and prevention systems.

No theory. No fluff. Just production. """

It's clearly slop, they immediately use effectively the same one again:

""" That last line isn’t a joke. There were charges I genuinely couldn’t explain. Elastic IPs we forgot to release. Snapshots from instances that no longer existed. CloudFront distributions someone set up for testing. """

No, human writers don't repeat this pattern every single paragraph. They use it at most across in a whole article.

BeastMachine 3 hours ago | parent [-]

Repetition is a very common tool in writing (ie 'I have a dream').

I'm just irked that it's being called out for AI slop because "I feel it in my bones!!"

There's a good chance it was written using AI -- should that matter? If the content is wrong/sucks, say that instead. If you're going to dismiss all AI assisted writing: good luck in the next decade.

jurgenburgen 21 minutes ago | parent [-]

Reading the same (very annoying marketing blog) style of writing gets old fast.

It’s like suddenly all memes are just the same meme and nobody makes their own memes because “AI does it better”.

The style of writing is an intrinsic part of communication, if you can’t critique that then what is content? We’re not machines sharing pieces of data with each other.

NERD_ALERT 8 hours ago | parent | prev | next [-]

> I just don’t understand it

Maintaining and updating your own hardware comes with so much operational overhead compared to magically spinning up and down resources as needed. I don’t think this really needs to be said.

sroussey 4 hours ago | parent [-]

I dunno… for setup, yes absolutely. One time cost in time. After that, not really.

p_ing 8 hours ago | parent | prev [-]

You need to factor in the data center, power, cooling, hands-on support, future growth, etc.

You're never just paying for the hardware.