|
|
|
|
|
by robert-zaremba
3908 days ago
|
|
At AgFlow (http://www.agflow.com), we've been using RethingDB for 2 years (since version 1.3 to 2.0). Eventually we migrated to PostgreSQL.
The query language from RethinkDB is very powerful. But it's nothing compared to SQL when it goes to expressiveness and performance (at least on PostgreSQL). ReQL is deceptive. It performs well as long as you don't embed JavaScript or don't do sophisticated joins (even based on indexes). When doing more complicated queries it becomes very ugly and slow. Our main motivations for migration was: * transactions
* performance
* tool kits around SQL
We are very happy after migration. Backup process is way faster.
I think there is only one place where RethinkDB is better then PostgreSQL: replication + automatic failover.
If your data is not in TB, then I wouldn't recommend Rethinkdb. World with relational DB, transactions, pl/sql, pub/sub, GiS, data constrains, stability... offered by PostgreSQL is way easier, reliable and offers better performance. |
|
I was about to ask. Are you guys running a single server deployment? Because, while I haven't used RethinkDB yet, it appeals to me precisely because PostgreSQL is an absolute pain to operate beyond single node setups. I've heard citusdb tries to tackle this, I don't know if they succeeded but still it doesn't look nearly as friendly as RethinkDB.