You are viewing a single thread.
View all comments
0 points

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

permalink
report
reply
1 point

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”.

permalink
report
parent
reply
0 points

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.

permalink
report
parent
reply
0 points
*

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.

permalink
report
parent
reply
0 points

They all offer managed kubernetes. So that would be my common divisor.

permalink
report
parent
reply

Selfhosted

!selfhosted@lemmy.world

Create post

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:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 3.4K

    Monthly active users

  • 1.6K

    Posts

  • 14K

    Comments