2 ms·
I still struggle for why someone would go RethinkDB over Hardoop. If you have the "Big Data" issue for using a Non-SQL DB (Another struggle of mine to find a cl
by baldfat 12y ago
I still struggle for why someone would go RethinkDB over Hardoop. If you have the "Big Data" issue for using a Non-SQL DB (Another struggle of mine to find a clear case for its use).
Why go RethinkDB when you limit what you can do with your data at the start. You can't do so things but the big one for me is you really can't do statistical analysis (Author pointed it out in the article). Why have a Non-SQL that really hinders the biggest selling point for the non-SQL DB? Wouldn't it just be better to use a SQL and expand the scheme horizontally???
Serious question that I don't understand.
- mglukhovsky 12y agoRethinkDB and Hadoop solve fundamentally different use cases. RethinkDB is designed for building scalable, realtime apps -- the query language, realtime push features (e.g. subscribing to queries), and clustering are purpose-built to help developers build and scale realtime apps. Hadoop is designed for distributed processing of large data sets, and is generally used for analytics workloads and data processing. NoSQL really just means "not using SQL". A lot of projects fit under that umbrella, including graph databases, key-value stores, document databases, and analytics databases, and they all address very different use cases.
- ma2rten 12y agoFirst, this is about scalability of your application and not your data analysis. If your application itself has a lot of writes, it may require to shard your SQL database. That may be easier using NoSQL. Also, NoSQL has advantages other than scalability. RethinkDB has a more pleasant query language (arguably), shamelessness (meaning it is easy to add a column), build-in ui, ...