this post was submitted on 10 Sep 2025
161 points (99.4% liked)
Technology
75041 readers
2912 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I can't argue, but there are benefits.
If you need something running 24/7 then on-prem may work out cheaper for you. Keep in mind you need a team of server monkeys to keep that running, and your company's security certifications will come nowhere near that of a major cloud provider.
Cloud is good for elastic workloads. And you can save money that way if you're set up for it. A simple lift and shift will always be more expensive. But doing things like moving build tasks to spot instances and auto scaling capacity in peak periods is a huge win. No need to over provision your DC and no need to upgrade your hardware -- generally AWS releases new products at roughly the same price as old but with increased performance. You get upgrades "for free"* with no capex.
Again I'm not saying that your circumstance means that cloud isn't more expensive. But there are medium term benefits.
AWS refused to offer hybrid as an option for years. They've changed their tune in the past 5 or so. No reason not to take advantage and do what mix makes sense for you.