I think your post proves the theory that they have a lot of product education work to do. It's not just about scaling. IMO it's about teaching the vast armies

I think your post proves the theory that they have a lot of product education work to do. It's not just about scaling. IMO it's about teaching the vast armies of software developers that work on proprietary line-of-business software that there is variety in data stores and that they should be using the right tool for the job. I shudder to think about how many EAV anti-patterns have been implemented on top of relational databases. Or how many 1-table-per-X databases there are. Or how many "json" columns and "blob" columns and "xml" columns have been added to otherwise innocent tables who did not deserve that kind of abuse. That alone -- educating and giving tools and support to engineers outside of the tech industry -- is no easy task.