3 ms·
Maybe I do not get your point but I have a complete opposite opinion. If you do not know about your clients' queries, you are better off with SQL since it enabl
by rwoerz 6y ago
Maybe I do not get your point but I have a complete opposite opinion. If you do not know about your clients' queries, you are better off with SQL since it enables clients to query exactly the data they need. If you know about future queries, you can shape your object or document storage or db beforehand to match these queries.
- justsomeuser 6y agoI agree with you. SQL allows for a much larger set of possible unknown-at-design-time queries as the data is broken down into atomic units. With a document store, you often find yourself de-normalising and copying data to new collections on-write to deal with the limited query language. This means your writers often implicitly encode the possible queries. As an example, in Redis if you need a 3 way join/filter, you will either a) have your application read all the data and filter it or b) maintain the filtered collection via writers copying the data.