Having worked somewhere with an AWS spend of $30k/mo on _virtually nothing_, I can attest to this. I think most of it was sales demos that never got cleaned up.
Converting your OpEx to CapEx is not a remedy for sloppy bookkeeping.
But if it significantly reduces total cost, it could still be a useful bandaid.
Most people who can do this (aren't as entrenched in AWS) end up moving to a cheap VPS provider so that they don't end up having to pay for all the internetworking, facilities, throw redundancy out the window, and then still have to pay the IT burden to heavy-lift all their workloads to this whole new "Oxide" system.
Re:Oxide: The Cloud Computer
by omarfarooq on Thursday October 26, 2023 @12:52PM
(#38028326)
> end up moving to a cheap VPS provider
Like which?
Hetzner, Linode, Rackspace, take your pick.
If those subdivisions aren't capable of reducing their AWS usage how do you imagine that they are capable of migrating to an Oxide rack?
Or in other words, is migrating to Oxide somehow assumed to be easier than migrating to some other non-locked-in cloud infrastructure?
Re:Oxide: The Cloud Computer
by TimTheTinker on Thursday October 26, 2023 @05:35PM
(#38031999)
Yeah, my example communication was a bit contrived. More likely a centralized IT group would assist when a division's IT isn't able or willing to spend cycles to reduce their AWS spend.
But even so, the point stands. There's a lot of non-wasteful AWS spend happening that is frustrating when you look at the raw numbers and consider how much cloud capability you could outright buy from Oxide and have a similar developer experience.
Oxide appears to be a shoo-in for companies that used to run a bunch of racked Dell/HP servers, migrated to AWS, hate their monthly AWS bills, and still have the server rooms they used to have.
"Hey subdivision A, could we buy a few Oxide racks and move your workload there from AWS? It looks like they would have all the storage and compute you need. Yes? Ok, in 36 months we'll pay your current IT department employees a bonus of 50% of whatever it has saved us vs your current AWS budget."