codebycliff
commented
5 years ago Yeah, it's hard to have an idea of a comparison without extracting out the connection handling. It seems more bloated currently, but that would go away with some extraction.
Either way, any reason to keep this around at this point?
tegandbiscuits
This is a small example using RethinkDB instead of Postgres with Knex.
I'm interested in rethink because it seems a bit like Firestore but less shit. I thought this example was really easy to get going, especially the setup script.
Major reservations about it due to the NPM package not being updated in 3 years. The project itself has small (seemingly responsive) development, and is working to a 2.4 release. It seems like they want to continue development on it, but there's not a big community and not a lot of funds, so lots of people are asking or think it's dead. Though part of me thinks that adding a project that uses it, and us talking about it would help keep it alive. Plus this more or less has an end date, so it's not like we'd be too invested in it anyway.
I also don't know how this would affect deployment. I think I could stand a bit of configuration, but if it's very hands-on for setup and maintenance then I wouldn't want to use it.
A fairer example would need to look into writing a test to see how that goes, and abstracting the connection creation and closing. The example projects use Express so create and close the connection in middleware. There should be equivalents in Hapi.