I'm reminded of this anecdote I had with a colleague a while back. He was railing against MS Exchange's rise back in the 90s, and how Novell Netware was better and that he was forced to switch their org to MS Exchange, back then, solely because "His CIO read it was the future in a magazine."
And so it was. Today, Netware's dead.
Could have been a self-fulfilling prophecy, and not something that would have happened without CIOs reading that magazine.
Novell eventually tried to catch up by grafting their proprietary networking features onto Unix but that was too little, too late. The CIOs who started migrating off of NetWare early were the smart ones.
I ported a C++ server and struggled with the only available C++ Compiler for Novell (Watcom). Debugging meant staring at core dumps. Novell bought SUSE too late.
These companies demand a premium over "rolling your own" or "integrating a pile of better at solving a specific problem" products. In some cases the premium is well earned, in others it's just rent-seeking monopolist behavior, depending on how mature the product space is.
Itβs confusing because it can apply to landlords who also seek to restrict supply, and people then conflate the former with the term.
Of those companies listed, maybe you can finger Oracle for their shenanigans with Java.
On the continuum of "innovative product solving hard problem" to "Rent seeing monopoly" AWS is still in the "build the mouse trap" phase while oracle's half way to CA.
Oracle licensing on the cloud can be byzantine. In part because their sales people don't seem to all have the same understanding.
https://techcommunity.microsoft.com/t5/data-architecture-blo...
(read the comments!)
Of course, license true-ups in my experience are allowed the latitude of, "Whatever you can get them to agree to". I've heard a few times Oracle sales folks trying to pressure companies into buying licenses for all physical machine cores for the host underneath their VM's in the cloud. Which is, frankly, malarkey and not even supported by their own docs. (Apparently this is how it is licensed on-prem if you own a VMWare cluster or something, but they carve out an exemption specifically for cloud hosting in their docs - but they try anyways)