no thanks. i'd much rather trust postgres to handle things like foreign keys, unique constraints, transactions, and other goodies than the application, which is is what ends up happening when you try to do this in a key:value store.
But then there the special people out there, they spend hours blogging about their personal opinion on how the giant grey blob KV DB can solve world hunger. Because it's all they know, they are afraid of change, they are afraid of ~ gasp ~, having to learn outside the box they dug themselves into, or they think they are these amazing super programmers that have the answer to everything. And then theres that write all this fluff for their resumes without actually knowing what they are doing but the senior engineer made them use it.
Engineering sucks.
Because many "engineers" do not have a solid understanding of the field, companies have been exploiting that by using and promoting solutions that would have been otherwise dismissed with very annoyed faces. Even docker would have been dismissed, as "cool but it has safety issues, so go home and redo your implementation".