What proprietary databases (and the Lord's of data fiefdoms in large enterprises that control them) fail in IT isn't necessarily production stability and perfor

What proprietary databases (and the Lord's of data fiefdoms in large enterprises that control them) fail in IT isn't necessarily production stability and performance. It's the ridiculous hoops you have to jump through to spin up a development insurance, a qa/unit test instance, to integrate with build pipelines, to run locally or in the cloud. If you're trying to diagnose something really hard, like intransigent performance or debugging issues , and you need to spin up a near copy of production to run big tests, well have fun getting that by your license sever or the license audit.