This discussion has revolved aroud the percore licensing issue, not the RDBs...
The legacy theme is bound to licensing, not the fact they are RDBs. Nowadays you are really not bound to commercial licenses, unless you have to cope with legal issues. The landscape and mindest has changed from "don't even think of doing business w/o Oracle" to "let's just push it on a pgsql (or mysql/maria whatever)". Is there a percore issue?
I'd be curious if there's any data to back up this statement if its available. Most commercial projects very much have a list of supported Databases. Now that is not to say the landscape is not changing. A large example I can think of is VMware vCenter. For a long time, vCenter was only supported on big-iron MSSQL and Oracle SQL Databases. VMware got tired of losing their cut of the pie to extra costs associated with the Database, so they have their own version of PostgreSQL called vPostgres that they now use to do the Database themselves. They also used to run on Windows and SUSE Linux, but they got tired of paying licensing to SUSE so they built their own Linux distro called PhotonOS and use that for their Appliance now.
That all above stated, the model works because of the application. VMware has worked hard over the years to minimize the impact of a corrupt or destroyed Database, to make it where restoring the Appliance is the quickest and safest way of getting vCenter back vs. troubleshooting the Database. This used to not be the case. You absolutely needed that transactional Database in-tact, and were required to purchase licensing to big-iron databases that assured that integrity.
The mindset changed because we're building better apps, not because of some sort of stigma. In the old days, the relational database was one of the most important pieces of a large company. It got all the resources (dedicated boxes long after almost everything else was virtualized), consumed a large portion of licensing costs, and had full time staff. Because all the applications said "just rely on the Database to keep me intact". Now we build better apps that recover better, that rebuild better, that restart better. That's when we started going "you know, we don't need these heavy iron DBs."
And that's a big difference. The reason you see mariadb and pgsql in a lot of places is because they can come
standalone in
a very small footprint. The only big competitor to those open source standalone DBs is Microsoft SQL Express, which has a very large footprint, and is resigned to running on Windows only.
When you have those DBs start running heavy iron workload, you find that there isn't that big of a cost-parity. Getting a supported MariaDB Cluster for instance is going to cost you 30K for 3 nodes. That can buy you 24 cores of Microsoft SQL Standard licensing at Advertised Price. While MariaDB can easily license better when developing huge DB servers, under 20 cores (which is the vast majority of SQL clusters), the Microsoft Licensing is actually better. And Microsoft also has their Server + CAL Licensing model, but you better have a Microsoft Licensing Expert available for navigating that quagmire.
The summary of all that is that
yes there are
absolutely times where you are bound to commercial support licenses. Those aren't going away anytime soon. And when you move your commercially supported Database to the cloud, you are still paying for a bundle of cores and RAM in a large number of cases.
Could that model be legacy someday and go purely to transaction billing? Sure. Is it even remotely close to be considered legacy today? Absolutely not.