If we become fully dependent on a service (shelter) and then the provider (landlord) jacks up the price, we may be quickly forced to switch services (homes) or be out of business (homeless).
About rent control, yup, it may have the ups and downs of real estate rent control :-)
I'm also wondering, with physical real estate, there is a tangible limit to how many people can rent the space, whereas SaaS seems to make up arbitrary user limits. But maybe I'm wrong, and there is a limited number of users because each user has variable costs—in the housing analogy, utilities like water, space, wear & tear on the place, etc., and in the SaaS space, customer service, server space...I can't think of any more but maybe they're there...
Do you think those resonate better?
Think about it, if the company has sysadmins that have been with the company for some years, have racked and are running most of their infrastructure, and all of a sudden they sign a long term contract with a cloud provider, why would they stay?
It’s possible that the company do not have all that infrastructure at all.
I also don’t see the importance of ‘knowledge to run things on premise’ for most people.
Technologies change very fast and if I can pay a reliable provider with a fixed price for the years that I intend to use it, why do I have to know how to use it?
If I can hire a gardener to take care of things for a reasonable price, I don’t care if I have any knowledge.
On skills I think there's a small risk of people not knowing how to manage/set up their own racks, but doing a passable job there isn't that hard. On general sys-admin stuff, cloud infrastructure seems to have parallels to hardware infrastructure, so it shouldn't be completely unfamiliar to set up a hardware router/network/linux server. There are definitely skills and details missing (remote admin tools for hardware maybe), but this doesn't seem like a big gap to bridge if $$$ is on the line?
Or they will be long gone due to google/aws/microsoft price dumping. In meanwhile, the openly accessible technology / know-how will be gone or hired by them and there will be no one left. Just look around, how many people you know that are capable of handling on-premise server? What about farm of servers without using any of google/aws/microsoft technology?
This just isn't something new.
It is just another case of "historia magistra vitae". We had this, 30-40 years back, we had centralized environment (have you heard about mainframes before?), due to huge price pumping the decentralized environment came in (personal computers, internet, on premise servers, storage, ...). IT needed almost 20 years to get out of the hooks of corporations and now we are all diving in into the latest "cool" thing - centralization, now backed up by advertising revenues and shady practices like not showing your company on google search.
This is not a joke: https://en.wikipedia.org/wiki/Google_litigation
And you can bet the history repeats itself.
---
Let me show you my point and where it is going, lets do a tiny experiment - use your router/firewall/whatever you are fond of and block the following ASNs:
AS40873,AS396982,AS395973,AS394639,AS394507,AS36492,AS36385,AS36384,AS36040,AS36039,
AS26910,AS26684,AS22859,AS22577,AS19527,AS16550,AS15169,AS13949,AS6432,
AS19448,AS16591,AS45566,AS43515,AS41264,AS394699,AS36987,AS139190,AS139070
then: AS16509,AS14618,AS7224,AS19047,AS395343,AS62785,AS58588,AS9059,AS8987,AS39111,AS38895,AS10124,AS264167,AS17493,AS135630
and: AS8075,AS8074,AS8073,AS8072,AS8071,AS8070,AS8069,AS8068,AS6584,AS63314,AS6291,AS6194,
AS6182,AS5761,AS45139,AS40066,AS397996,AS397466,AS396463,AS395851,AS395524,
AS395496,AS36006,AS3598,AS32476,AS31792,AS30575,AS30135,AS26222,AS25796,AS23468,
AS22692,AS20046,AS17345,AS14719,AS13811,AS13399,AS12076,AS35106,AS8812,AS200517,
AS58862,AS59067,AS52985
Now try to surf the internet. Casual style. As nothing happened.Baidu (China) and Yandex (Russia) will still work from search engines. Duckduckgo not (shame on you). As any other you know. "The internet" as you know it will stop to exist for you. You know what you have blocked with those ASNs? Only 3 companies. Google. Amazon. Microsoft.
For complete experience you can also throw in AS714,AS6185,AS2709 and AS63293,AS54115,AS32934 (Apple, Facebook), but those two are not really relevant.
Maybe this will be eye opening how much we have f* up the internet, something that should survive 3rd world war is now mostly in the hands of 3 companies. Now imagine they pull the switch.
Oh yeah, that bad it is.
I see people frequently quoting the bit about how the Internet was designed to withstand a nuclear war. But that quote was about packet switching. I.e. layer 2/3. Not layer 7. Application layer is, as you nicely demonstrate, very centralized, and was never immune to nuclear war.
My only response is that when I look at bigger orgs and places like Fortune 500 cos I still see/hear about home built server farms, so those people must be out there. I think maybe we get blinded in startup/SV land and only see people using cloud infrastructure but miss a huge, silent mass of people.
(Your reply with an unbroken word that spans larger than the page width forced my page to grow (horizontal scrollbar))
Thinking about it logically, the safest approach is always going to be build for on-premises infra first (or standard VPSs), then modify the code to support cloud services in addition, to get the added benefits of scaling at cheaper costs.
That way you can always switch back to on-premises if the cloud provider starts behaving terribly. Perhaps there is a performance hit, but at least you have an option.
Worth mentioning that there are some use cases that are only possible using cloud infra due to scaling constraints.
This is the approach I took building my SaaS. It’s more difficult initially, but I had an infra that could easily be moved. I was using my own version of backend queues etc, so modifying the code to switch to Amazon SQS would theoretically have been possible:
https://blog.markjgsmith.com/2020/11/26/looking-back-at-link...
These are changes that are happening on a timescale much larger than the average lifespan of a cloud-based product/system. I think people building things in the cloud know it, or at least feel it, and so just don't care about long-term - because in the long term they expect to be rich and/or doing something else. In the meantime, ooh cheap compute, billable as opex - let's build everything on it!
I’m no amazon apologist, but one thing I trust them to do is keep my things running as they are.
Ubuntu is actually heavily investing into MAAS (metal as a service) and so is Redhat with cobbler and foreman. So I'm guessing there's enough demand to justify their development (as every major cloud provider uses in house tools AFAIK)
It’s why google buys non intel chips. Come negotiation time there’s a serious threat they can leave. And there’s a serious rfp out to other vendors for pricing. Bringing their intel chip costs down.
Yes. You are right. The whole cloud deal is a try to rule out on premise infrastructure and once it is gone and everyone is dependent on it (due to lost of knowledge, and for cloud providers ideally when hardware vendors are no longer selling hardware to non cloud entities) harvest the dependent businesses left at their mercy and charge dearly (including for all the years before that). It is actually not even a complicated plan but it is staggering how many people are putting cloth over their eyes.