News for hackers. Stuff that matters.

A comment on RethinkDB: why we failed (2017). Parent comment

Re:RethinkDB: why we failed (2017) by WrtCdEvrydy on Saturday March 13, 2021 @12:38AM (#26444276)
Honestly, as the person who is ending up having to do the RethinkDB migration... it's the lack of an AWS hosted solution that killed it for us. Even the import is a great experience and moving to MongoDB wasn't too bad (after a bit of cleanup)
[ Parent | on HN ]
Re:RethinkDB: why we failed (2017) by nodesocket on Saturday March 13, 2021 @12:43AM (#26444304)
Interesting, RethinkDB was really easy to setup. Three EC2 instances (cluster), install their apt repo, and install. There were a few config options[1], but really minimal and clean.

[1] https://rethinkdb.com/docs/config-file/

[ Parent | on HN ]
Re:RethinkDB: why we failed (2017) by 411111111111111 on Saturday March 13, 2021 @03:10AM (#26444929)
The setup process isn't the reason people want to use hosted services, the maintenance is.
[ Parent | on HN ]
Re:RethinkDB: why we failed (2017) by WrtCdEvrydy on Saturday March 13, 2021 @01:43PM (#26448816)
Yeah, that's what we ran too, but there's a heavy internal push to use managed services.
[ Parent | on HN ]