I question if the NoSQL trend for transaction processing was misdirected. Under what scenarios do document databases offer true benefits over classical relational systems?
In my experience, NoSQL and document databases have proven advantageous in scenarios where the data schema evolves quickly and flexibly. The idea is not to replace relational systems in traditional transactional environments. Instead, they offer benefits in applications that primarily read and write large volumes of semi-structured data without heavy reliance on complex joins and relations. For projects where scalability and rapid deployment of changes are crucial, and where relational integrity constraints are less critical, document databases can indeed be very effective.
i think docs offer agilitiy when your data changes fast, but for solid transactional work, relational isnt easily replaced. it all boils down to what your app really needs even though nosql is cool for certain tasks