Why SQL is beating NoSQL, and what this means for the future of data

Re:Why SQL is beating NoSQL, and what this means for the fut... by jbergens on Wednesday September 27, 2017 @02:35AM (#15345378)

Complex analytics should probably be done in a db separate from the production db anyway. The analytical db could be an RDBMS, a datacube or something else.

[ Parent | on HN ]

Re:Why SQL is beating NoSQL, and what this means for the fut... by tn_ on Wednesday September 27, 2017 @10:08AM (#15347907)

Absolutely agree that if you're going to be manipulating the data w/ heavy complex analysis as well as a ton of data-points, it should occur not on the prod db.

I was referring to queries such as: User needs to get a list of pharmacies they've gone to in the past 2 months that carries x-medication. Not overly complex, but annoyingly more code that would have to be written + architected in NoSQL vs a relational db.

[ Parent | on HN ]

Re:Why SQL is beating NoSQL, and what this means for the fut... by degyves on Sunday October 01, 2017 @08:25AM (#15377537)

That's when having mongodb+RDBMS with the added complexity is really justified. On common cases, just drop mongodb and use the RDBMS for everything.

[ Parent | on HN ]