RethinkDB versus PostgreSQL: my personal experience
Good grief. Well this is a genuinely fascinating post containing a couple of absolutely terrifying insights:<p>"A RethinkDB employee told me he thought I was their biggest user in terms of how hard I was pushing RethinkDB."<p>Erm. If I were working for/a founder of a relatively small company using a product or service, especially one that's so critical to my own business, that is not the sort of thing I'd want to hear from the provider.<p>"Everything was a battle; even trying to do backups was really painful, and eventually we gave up on making proper full consistent backups (instead, backing up only the really important tables via complete JSON dumps)."<p>Holy crap.<p>Well, the story has a happy ending, and I think the point about the fundamental expressiveness of SQL is something that a lot of people miss in the mad dash to adopt "simpler" NoSQL solutions. I personally find SQL verbose and a bit ugly, but I still sort of love it because it's <i>hugely</i> powerful and expressive. I was perhaps 6 or 7 years into my career before I became comfortable with it, but I wish I'd thrown myself into learning it properly sooner because it is so incredibly useful.