Selfhosted
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:
- selfh.st Newsletter and index of selfhosted software and apps
- 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!
view the rest of the comments
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:
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".
Given the context of the article, the alternative suggestion isn't "set up your own server" but "use software that doesn't require a server", which sidesteps most of that list.
A bad command execution in a small IT shop will only bring down a couple of websites at most. A bad command execution in large cloud providers can literally make significant portions of the web unavailable, just by the sheer number of services dependent on it.
The same applies for most of the "practical realities" you noted out: Redundant infrastructure can only work as well as the software running on it. The convenience is not worth the risk.
You can't have it both ways. You're trying to call out all of the benefits of running your own infra, but then calling out the downsides of public cloud. Talk apples to apples or oranges to oranges. The point I'm making in the post you're responding to is that "rolling-your-own" as an organization, specifically a small or medium sized one, comes with risks that far outweigh the costs and risks of public cloud.
That is not the opinion of non-IT business leaders make decisions to the detriment of the advice of IT departments. You're ignoring that good IT decisions don't get to be make by good IT professionals. You're always limited to the budget and power granted by your organization. That is the practical reality.
cough.. whhhat.. all of those thing can and do occur in cloud-only companies. just because its someone elses hardware doesnt mean every single thing you listed isnt a risk.