this post was submitted on 06 Jul 2023
115 points (99.1% liked)

sh.itjust.works Main Community

7649 readers
9 users here now

Home of the sh.itjust.works instance.

Matrix

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] CodeInvasion@sh.itjust.works 4 points 1 year ago (2 children)

Have you considered the implications of hardware failure on uptime? And where the cost to maintain a physical hardware will come from? What about scaling requirements?

I'm not a network engineer, but I've been involved in the corporate argument of Cloud vs On-Prem. hosting for years now. The costs always come out better for Cloud when factoring in other indirect costs like facilities and labor.

Granted it's always been on the scale of hundreds of millions to billions of dollars, and I haven't run the numbers on smaller requirements. I just wouldn't want to expose additional points of failure in return for slightly lower monthly costs.

[–] Wats0ns@sh.itjust.works 2 points 1 year ago (1 children)

I think the cost always come out better for cloud for a given reliability level. But this is a volunteer run thing, so we won't mind if there is some more important downtime than on reddit or Twitter. I really do think that if your objective is not reaching 100% uptime but cost reduction, then on prem really becomes the cheapest option

[–] CodeInvasion@sh.itjust.works 0 points 1 year ago

A very good point! We don't need constant uptime. But I worry about the hidden costs of On-Prem, and worst case scenario where TheDude is on vacation somewhere and the instance crashes, it could be down for a while. It's also not a worry I would want to force on them either.

[–] Ajen@sh.itjust.works 1 points 1 year ago

He mentioned colo, so it sounds like he's already decided against on-prem.