3 ms·
That's all great until you need to perform a join.
by cglace 9y ago
That's all great until you need to perform a join.
- overcast 9y agoRethinkDB handles joins just fine :)
- elcritch 9y agoAs does couchbase. :-) Personally I like map-reduces.
- ifcologne 9y agoSo does the multi-model database ArangoDB. https://docs.arangodb.com/3.2/AQL/Examples/Join.html https://docs.arangodb.com/3.2/AQL/Examples/Join.html And some NoSQL databases speak SQL as well - without being relational. I like the JSON support in PostgreSQL a lot. Very easy to deal with unstructured JSON data while still using common attributes in a relational format. But there are more cases that one might think about - as a relational guy - that benefit from graph databases, document stores or optimized time-series databases.
- throwaway_idiot 9y agoIt's hysterical you would bring up RethinkDB as a positive example. How does it handle scaling to millions of rows in a real world environment? Or what about data integrity? Or backup management? or user permissions? Answer: Pathetically. Edit: Also, RethinkDB handles complicated queries EXTREMELY POORLY! You can write toxic queries that will tank your entire database, and the monitoring is so poor it's impossible to figure out what is causing it. Like seriously, have you even written anything in RethinkDB? I built a company on it, and it is just trash software and all of my biggest technical debt stems from using that trash database. "Handling joins just fine" What are you TALKING ABOUT? It is SO SLOW and they state explicitly in the documentation that you shouldn't use NoSQL databases if your data is relational.
- deleted 9y ago[deleted]