• 0 Posts
  • 237 Comments
Joined 1 year ago
cake
Cake day: August 16th, 2023

help-circle


  • It’s very much the Oracle model.

    A long time ago, Oracle DB could handle workloads much, much larger than any of their competitors. If you needed Oracle, none of the others were even a possibility. There are even tales that it was a point of pride for some execs.

    Then Oracle decided to put the screws to their customers. Since they had no competition, and their customers had deep pockets (otherwise they wouldn’t have had such large databases), they could gouge all they wanted. They even got new customers, because they had no competition.

    Fast forward and there are now a number of meaningful competitors. But it’s not easy to switch to a different DB software, and there are a ton of experienced Oracle devs/DBAs out there. There are very few new projects built using Oracle, but the existing ones will live forever (think COBOL) and keep sucking down licensing fees.

    VMware thinks they are similarly entrenched, and in some cases they’re right. But it’s not the simple hypervisor that everyone is talking about. That can easily be replaced by a dozen alternatives at the next refresh. Instead it’s the extended stack, the APIs and whatnot, that will require significant development work to switch to a new system.


  • This is actually a regional bit of language, specifically the region of the US. The term ‘state’ originally meant (and in some places, still means) an independent and sovereign entity/government. Under the terms of colonial America, each state was truly independent, so the term makes complete sense. Even the original attempt at uniting the colonies (under the Articles of Confederation) maintained that independence.

    But that failed and was promptly replaced by the US Constitution, which made the states much more like provinces. They became a piece of the whole, with significant influence from the larger entity. But we kept the term “state” when referring to them.