5 ms·
Vast majority of cases I've come across, if not all of them, only suffer from any reliance on 90s era RDBMS systems. And it's never about JSON, it's about late
by zzzcpan 9y ago
Vast majority of cases I've come across, if not all of them, only suffer from any reliance on 90s era RDBMS systems.
And it's never about JSON, it's about latency and resilience, about being able to simply add and replace nodes, about just working in a modern distributed environment.
- cglace 9y agoThat'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]
- collyw 9y agoHow many systems actually need a distributed database though? In my experience its usually resume driven development that makes the choice to go NoSQL.
- projectileboy 9y agoDear God, this. 90% of the people reading this (or more) - myself included - are currently working on a system that averages fewer than 100 concurrent users. I’ve worked on big systems, and DBs like Cassandra are great, and absolutely have their place, and that place is likely not your system. Quit over complicating everything, please. Please.
- federicoponzi 9y agoI love this comment, because it's exactly how I feel about when people talk about these systems, designed for big scale.
- deleted 9y ago[deleted]
- lern_too_spel 9y agoAnybody who needs more availability than an individual instance can provide.