> If your data has a one-to-many relationship, then Document Database (NoSQL) is more appropriate. Maybe. Probably not. But what happens when you want to query

> If your data has a one-to-many relationship, then Document Database (NoSQL) is more appropriate. Maybe. Probably not. But what happens when you want to query the inverse many-to-one relation? Unless your document store is effectively indexing these one-to-many relations as another document store with inverse relations (at which point you have an RDBMS regardless of what you call it), it’s probably going to be wildly inefficient.