Tired of relying on Big Tech to enable collaboration, peer-to-peer enthusiasts are creating a new model that cuts out the middleman. (That’s you, Google.)
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
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.
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
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”.
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.