"Blockchains" are not just distributed databases. They are also distributed, open APIs, and consensus mechanisms for updating and managing the functionality that controls those APIs and the data that they produce.
I think about it this way: if you have one company that creates a database that many people use to build businesses around, then that company now holds a lot of power over the people who chose to build there. I believe that those people should have a say in the direction of the APIs that input/retrieve data, and ultimately should have some say in how long that database persists. The idea that we allow single entities to permanently control datasets seems absurd to me.
Now, from an engineering management perspective, think about how you manage multiple teams who have different agendas, different priorities, and different needs for those APIs and the child data. How do you govern that? How do you ensure that all nodes that replicate this data set and the APIs are up to date and not doing funny business?
This is all stuff that the decentralized community (web3) is trying to figure out together. It's DEEPLY interesting and ABSOLUTELY not "a few minutes work".