3 ms·
I would call joins a bug of relational rather than a feature. If you have all the data in one collection, you don't need or want joins. For transactions, we
by gibsonf1 4y ago
I would call joins a bug of relational rather than a feature. If you have all the data in one collection, you don't need or want joins. For transactions, we do that server side (in our own system) as we have what we call temporary awareness created for each request that only writes when all operations have completed successfully before importing the state changes into primary awareness for that user.
- simonw 4y agoEvery large system I've ever encountered that's built on a NoSQL system such as MongoDB or Elasticsearch has inevitably ended up reinventing joins, poorly.
- gibsonf1 4y agoWe have 1 collection with 4 doc types (attribute, state, event, process) and 14 relations between them, so a join concept makes no sense for us. I think the schema is the key issue in having success vs not. (Apache Solr - billions of docs)