[gigatexal]

Cons? It's dead -- or so I thought it was. Seems it was open sourced and is getting regular updates and releases. I really liked the idea of it when it came on the scene but have not looked at it yet.

What is your use-case? Why do you think RethinkDB would be good for it?

[m33k44]

> What is your use-case?

Want a DB to store highly connected massive graph structure with requirement of auditing and analytics.

> Why do you think RethinkDB would be good for it?

It is a document store, supports changefeed, is distributed and fault-tolerant, supports geospatial types, auto-sharding and can scale horizontally.

[gigatexal]

Can you do a PoC and see if it will work? One of the things I learned in econ is you can't really understand what price a market will support without putting up a store and selling something.

[m33k44]

Yes, I will be doing that. But thought I will ask the wider community here before proceeding. It will help me avoid problems others have faced.

[gigatexal]

Rektide's comment about data corruption is troubling, but perhaps they have fixed those. I wonder has RethinkDB been Jepsen tested recently? 2.2.3 was tested, seems ok, latest version is 2.4.x https://jepsen.io/analyses/rethinkdb-2-2-3-reconfiguration

[gigatexal]

You've convinced me to take another look at it. I had written it off. I thought it was dead.