We have already seen the effects of over-reliance on a few CDNs and cloud providers: One bad push, one ill intentioned employee and potentially entire portions of the web might become unaccessible. That by itself should have been the end of this business model long ago
this post was submitted on 04 Aug 2023
0 points (NaN% liked)
Selfhosted
39167 readers
387 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
So you're recognizing that a bad command execution can exist in CDN or cloud provider, but where is your recognition of the tens of millions off bad command executions that happen in small IT shops every month?
I looks like you're ignoring the practical realities that companies rarely ever:
- hire enough support staff
- hire enough skilled staff
- invest in enough redundant infrastructure to survive hardware or connectivity failures
- design applications with resiliency
- have high enough rigor for audit, safe change control, rollback
- shield the operations stupid decisions leads impose because business goals are more important that IT safety
All of these things lead to system impacts and downtime that can only come from running your own datacenters.
The cloud isn't perfect, but for lots and lots of companies its a much better and cheaper option than "rolling your own".
If no legal issues stand in your way and your uptime requirement warrant the invest, you can design and host your system across multiple providers. So instead of "just" going multi-datacenter within for example Azure, you go multi-datacenter across Azure, AWS, GCP, etc.
The problem with that, is that you now have to maintain virtual infrastructure in many different syntaxes. And features of one do not exist in another.
Plus things like cash and session do not cross those boundaries.
They all offer managed kubernetes. So that would be my common divisor.
“The cloud” does not exist, it’s just someone else’s computer.
I mean…
I gotta say, I really hate it when people say this statement.
That’s a pithy saying, but the cloud is a totally different model than a “computer”.
The concept of “cloud” (generally) has its own way of interacting with tooling, it’s got a huge economy of scale that brings resiliency, a ton of interconnected services, etc. There’s more to it than just computers.
That’s like saying “the Highway doesn’t exist, it’s just someone else’s driveway.”—yeah, but there’s more to it than just streets.
I work in a company that runs an own cloud for most of it’s business operations and for customers. I know where the data center is and when I go there I SEE the computers running the cloud.
It’s physical hardware running virtual machines and storage servers, and network switches with absurdly and unnecessary complex configuration, all owned by, well, someone else (the company).
So yes, the features of “the cloud” are distinct from your everyday stuff done on the computer sitting under your desk, but it really is just someone else’s computer running “the cloud”.
Isn't part of "the cloud" being able to scale? That only works if there is a large(r) shared infrastructure layer. Of course I can have my own datacenter where I host my clustered services. But if I decide I need 20% more resources, I need to order and setup 20% more machines. On the other hand, if I just keep 20% machines idling around for the chance that I might need to scale up, I waste a lot of money.