7 ms·

Open-RethinkDB meeting notes

158 points by deepanchor 10y ago

bcantrill 10y ago
It's great to see that getting to an open source foundation is a top priority! As a member of the CNCF's technical oversight committee (and as someone who personally loves RethinkDB), I would love to champion RethinkDB for the CNCF -- but it matters much more to me that it gets to an open source foundation than it is that it lands at the CNCF in particular. RethinkDB team: please reach out to me or to any other CNCF TOC member if we can help!
- deepanchor 10y ago
  From an outsider's perspective, CNCF seems like it would be a great fit for a project like Rethinkdb: it looks to have the forward momentum Rethink needs right now, and the proximity to other high profile projects like Kubernetes could encourage adoption.
  - philips 10y ago
    I would love to see a RethinkDB Operator created[1]! [1] https://coreos.com/blog/introducing-operators.html https://coreos.com/blog/introducing-operators.html
cyberferret 10y ago
I am not a stakeholder, but I just wanted to congratulate you on keeping the momentum going on the Open-RethinkDB project. I've seen several attempts to restart a stalled/dead OS project in the past, so I realise how much energy it takes to keep the ball rolling after the initial flurry of activity/outrage/frustration etc. RethinkDB is something we were looking at for a large project. In one way I am glad we didn't choose that platform for it, but in another way, the efforts by the open source community to keep it alive has given me confidence to revisit the platform for future projects.
- kinkdr 10y ago
  > RethinkDB is something we were looking at for a large project From the comments in HN it feels like this was always the case for RethinkDB; folks looking at it, admire it, thinking about using it in their next project but, for one reason or the another, never ending up using it. Which is really a pity. I don't know about the others, but I am really curious to know why you ended up not picking RethinkDB for your project.
  - cyberferret 10y ago
    Good question, and one that is worthwhile asking as part of the post mortem process. In our particular case it is because I (as lead technical person on projects) come from a 30+ year background in SQL. Moving to NoSQL is always a point of trepidation for me purely form a comfort and familiarity angle. I must say though, in our investigation of NoSQL systems for a couple of projects ReThinkDB (and PouchDB for another mobile project) were the two that seemed to stand out, and seemed to make installation and testing easy, as well as remove a lot of the barriers to dipping a toe in the NoSQL ocean. So, end of the day it wasn't really a technology issue, but rather came down to familiarity and habits. NB: For the mobile project, we went with Back& (backand.com) which is essentially a NoSQL wrapper around a MySQL database that we have running behind it. It helped me to get my head around NoSQL while still letting our DBAs build out the data structures in pure SQL. Working well so far.
  - jinjin2 10y ago
    We were considering RethinkDB for a mobile project, but ended up using Postgres on the backend and Realm in the apps with a custom REST API in between. This worked out really well for us, apart from all the work on implementing our own REST based sync (this was before Realm launched their backend product, which might have made a lot of that work unnecessary). The reason we ended up with Postgres over RethinkDB was that our data model was very relationship heavy in ways that were easier to represent in a relational database than with RethinkDB's document model.
    - cyberferret 10y ago
misterbowfinger 10y ago
For those involved, any word on when they'll be putting up a post-mortem on how they ended up shutting down?
- nodesocket 10y ago
  I am also really curious, and think it could be a valuable asset to the greater startup community. The best tech/product and design doesn't always win.
zubairq 10y ago
yep good to see clear info about the future so soon after joining stripe!

158 points by deepanchor 10y ago

It's great to see that getting to an open source foundation is a top priority! As a member of the CNCF's technical oversight committee (and as someone who personally loves RethinkDB), I would love to champion RethinkDB for the CNCF -- but it matters much more to me that it gets to an open source foundation than it is that it lands at the CNCF in particular. RethinkDB team: please reach out to me or to any other CNCF TOC member if we can help!

deepanchor 10y ago
From an outsider's perspective, CNCF seems like it would be a great fit for a project like Rethinkdb: it looks to have the forward momentum Rethink needs right now, and the proximity to other high profile projects like Kubernetes could encourage adoption.
- philips 10y ago
  I would love to see a RethinkDB Operator created[1]! [1] https://coreos.com/blog/introducing-operators.html https://coreos.com/blog/introducing-operators.html

cyberferret 10y ago

I am not a stakeholder, but I just wanted to congratulate you on keeping the momentum going on the Open-RethinkDB project. I've seen several attempts to restart a stalled/dead OS project in the past, so I realise how much energy it takes to keep the ball rolling after the initial flurry of activity/outrage/frustration etc. RethinkDB is something we were looking at for a large project. In one way I am glad we didn't choose that platform for it, but in another way, the efforts by the open source community to keep it alive has given me confidence to revisit the platform for future projects.

kinkdr 10y ago
> RethinkDB is something we were looking at for a large project From the comments in HN it feels like this was always the case for RethinkDB; folks looking at it, admire it, thinking about using it in their next project but, for one reason or the another, never ending up using it. Which is really a pity. I don't know about the others, but I am really curious to know why you ended up not picking RethinkDB for your project.
- cyberferret 10y ago
  Good question, and one that is worthwhile asking as part of the post mortem process. In our particular case it is because I (as lead technical person on projects) come from a 30+ year background in SQL. Moving to NoSQL is always a point of trepidation for me purely form a comfort and familiarity angle. I must say though, in our investigation of NoSQL systems for a couple of projects ReThinkDB (and PouchDB for another mobile project) were the two that seemed to stand out, and seemed to make installation and testing easy, as well as remove a lot of the barriers to dipping a toe in the NoSQL ocean. So, end of the day it wasn't really a technology issue, but rather came down to familiarity and habits. NB: For the mobile project, we went with Back& (backand.com) which is essentially a NoSQL wrapper around a MySQL database that we have running behind it. It helped me to get my head around NoSQL while still letting our DBAs build out the data structures in pure SQL. Working well so far.
- jinjin2 10y ago
  We were considering RethinkDB for a mobile project, but ended up using Postgres on the backend and Realm in the apps with a custom REST API in between. This worked out really well for us, apart from all the work on implementing our own REST based sync (this was before Realm launched their backend product, which might have made a lot of that work unnecessary). The reason we ended up with Postgres over RethinkDB was that our data model was very relationship heavy in ways that were easier to represent in a relational database than with RethinkDB's document model.
  - cyberferret 10y ago

misterbowfinger 10y ago

For those involved, any word on when they'll be putting up a post-mortem on how they ended up shutting down?

nodesocket 10y ago
I am also really curious, and think it could be a valuable asset to the greater startup community. The best tech/product and design doesn't always win.

zubairq 10y ago

yep good to see clear info about the future so soon after joining stripe!