RethinkDB[0] looks like a "too good to be true" type of database. Anyone using it in production? What is your experience like? What are the pros and cons?
[0] https://rethinkdb.com
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?
I wouldn't: https://mxstbr.com/thoughts/tech-choice-regrets-at-spectrum/
Just use Postgres.
I really liked the idea of RethinkDB back in the day but sadly had a lot of performance issues with it shortly before it was sunset, so it went off my radar. TIL that it's still updated and continues to thrive as an open source solution.
Before my time but we had some extended outages owing to rethink. We pushed most of our documents into postgres jsonb. We got pretty far relationalizing the data when I was here, but there was some bad old data that wasn't porting & debates about if the architecture was right, & we gave up the relationalization effort, after a squad worked on it for over a year, basically at the go/no go mark. Sad stuff. But the architecture was pretty meh.
I might suggest checking out ArrangoDB if you are RethinkDB interested. Similar capabilities ish. Very active development. They up sell pretty heavily into the Enterprise offering but the community one is still quite capable.