RethinkDB is shutting down

Post by bpicolo » Thu, Oct 06, 2016, 1:01 PM UTC

pluma wrote: post #253

guessmyname wrote: post #43

Earlier quoted context omitted.

I believe this is because the Node.JS community still recommends MongoDB as the perfect database engine for their projects. There is even a name for their stack — MEAN, MondoDB + Express.JS + Angular.JS + Node.JS — which is kind of ironic because considering the rapid evolution of the JavaScript ecosystem having an acronym like that will make no sense in a couple of months since now people prefer React-like libraries…

Don't laugh -- there's now a thing called MERN, which is basically MEAN with Angular replaced by React. The entire sell of MongoDB in the Node community seems to be "it speaks JavaScript and you can store objects in it". Which of course fails to take into account any of the strengths and weaknesses of MongoDB (in the latter case especially the lack of cross-collection transactions or fast joins -- which in my experie…

Post by habitue » Thu, Oct 06, 2016, 1:10 PM UTC

kabes wrote: post #272

habitue wrote: post #180

Earlier quoted context omitted.

That's what literally everyone does for changes on mongo, from Meteor to Firebase. There isn't another way

Honestly interested: how do you know Firebase works that way and do you have any links to more info about how Firebase works?

Post by samdung » Thu, Oct 06, 2016, 1:27 PM UTC

nathancahill wrote: post #269

samdung wrote: post #266

RethinkDB fits into the category of products i love but do not use because i do not want to manage the underlying servers. I've moved to Firebase and other 'services' on the Google, AWS clouds. Given that this is the way many of us are operating (i.e. 'moving to the cloud'), i wonder what the state of open source software is going to be in the coming years ...

I'd like to caution you about doing this. Look at Parse. Not owning the "underlying servers" your product runs on is a liability, not a benefit.

Post by falcolas » Thu, Oct 06, 2016, 1:35 PM UTC

samdung wrote: post #275

nathancahill wrote: post #269

Earlier quoted context omitted.

I'd like to caution you about doing this. Look at Parse. Not owning the "underlying servers" your product runs on is a liability, not a benefit.

We did weigh the options for/against but went with Firebase because they got acquired by Google and the Founders (and Google) made public promises not to shut it down. Again, we don't rely entirely on Firebase. There is always another database (like AWS Dynamodb or Google Cloud Datastore) in the picture ... but again all hosted in the cloud ... not much servers to manage for my team. If Google and AWS shut down ... t…

Post by elcritch » Thu, Oct 06, 2016, 1:43 PM UTC

erichocean wrote: post #134

jkarneges wrote: post #119

Earlier quoted context omitted.

If I had to speculate, I'd say that they spent a long time in development before monetizing, longer than investors were willing to entertain. It's hard for a B2B company to raise a Series B without a thoroughly proven revenue engine. I don't know how this could have been fixed though. Databases are hard to develop and it's a tough market to crack. Enterprises aren't going to buy an incomplete product, especially not…

> Horizon is a bit of a mini-pivot When Horizon was announced, that's when I stopped even considering RethinkDB for new projects (even if it was a good fit, feature-wise). Call it a "business smell", but I'm not surprised to hear they've wound the business down.