3 ms·

I'm confused. You appear to have repeated and expanded upon my position but are also inferring it's wrong. Am I missing something here?

• hardwaresofton 4y ago
  > Mongo (similar for other NoSql propositions) is most suitable for specific data access patterns. > The most obvious one being where you are requesting data and related data based upon a unique business identifier. NoSql DBs mostly make this both trivial and fast. I don’t think that’s right though? Requesting data and related data is the purview of RDBMS, unless your example was a completely denormalized single object (I know Mongo supports links between objects as well but that doesn’t seem to be what you’re saying?) Also the line point about SQL based databases being relevant when reporting and aggregation misses the importance of relations and operations in relations that is the point. Maybe the comment was focused in on “SQL” rather than using it as a shorthand for “relational database” like most people do. Yes SQL makes aggregation and reporting easier but it’s primary job is data retrieval, and in most cases via an identifying primary key.