We wanted to share RethinkDB's next steps in our new home with The Linux Foundation.
We've also had a lot of folks ask if they can donate to support the project. Stripe has generously offered to match up to $25k in donations (which will help fund server costs and future development.) You can learn how to contribute to the project with OSS contributions or donations here: https://rethinkdb.com/contribute
Yes, I use it in my upcoming project, which is just a regular, (no real-time sensitive) webapp and RDB is perfectly usable as a regular NoSQL database.
I really like the fact that you query the database by calling methods on an object rather than passing strings to it, feels more like actual programming and protects you from injection attacks.
The WebUI and easy scalability are great features as well.
It and CockroachDB, (for more traditional SQL, same scaleability benefits), are the databases I am most excited about, but I seem to prefer ReQL to SQL despite being vastly more familiar with SQL :-)
Strong promises about consistency
Nosql with joins
Atomic changefeeds (real time)
A great functional query language (reql)
Great admin UI
Simple auto sharding that actually works
We use changefeeds but just to update Elasicsearch. The key value offer is the very powerful query language which feels right at home in Node, strong robustness, and real proper join support with NoSQL.
Mike and Slava, you guys are so great! You've worked overtime to secure social confidence in RethinkDB for others when the engineering talent alone was good enough. You guys are so admirable and hard workers and such a good role model to others.
I haven't used ReThinkDB yet, but I know that projects I have or will rely on do. Therefore, I donated and I encourage you to do the same! It helps that I met Slava at a bar in Mountain View once and he was really nice to me =)
I also donated... I haven't been able to use it in a workplace project (yet), but have to say following several of the issues/resolutions, it would be my first choice today for most scenarios.
To add to that: one of the great consequences of this change is that a large amount of RethinkDB source code that was previously unavailable as open-source code (including some unreleased features for RethinkDB, copious amounts of artwork and content, and build / performance scripts) will now also be steadily open-sourced.
We felt that it was too important to let the work we created have a life of its own and establish its own life in the open-source community. It's wonderful to see this finally happen.
Some of the code and content was heavily used internally, but we never invested time to properly package it for public consumption.
We also briefly had a closed-source version of RethinkDB that has a few useful features for larger teams: we're excited to be able to merge these back into the project.
Hey everyone, thanks to the rest of the RethinkDB leadership team and the CNCF for their hard work! This wouldn't have been possible without a lot of effort from our dedicated community.
We've had a lot of folks ask if they can donate to support the project. Stripe has generously offered to match up to $25k in donations (which will help fund server costs and future development.) You can learn how to contribute to the project with OSS contributions or donations here: https://rethinkdb.com/contribute
I'd like to point out that the OP of this comment is Mike the RethinkDB co-founder. While the company may have perished, his spirit for the project only got larger. Everyone buy Mike a beer.
Don't use it, never have. Sent a coffee anyway just to say thanks! Thanks for caring and thanks for releasing under a license that allows all to use it!
That announcement post now has its own thread: https://news.ycombinator.com/item?id=13581375. Normally, of course, we wouldn't have two threads so closely related on the front page, but the topics do seem distinct in this case and they're both pretty major.
Thanks for doing that! I think that these topics are indeed distinct, and it's important that once people see the news, they see the leadership's plan for RethinkDB. I've been really impressed with RethinkDB's leadership through this arduous (and often uncertain) process, and really looking forward to seeing where they and the community take the project!
We're writing to let you know that the group you tried to contact (oss) may not exist, or you may not have permission to post messages to the group. A few more details on why you weren't able to post:
* You might have spelled or formatted the group name incorrectly.
* The owner of the group may have removed this group.
* You may need to join the group before receiving permission to post.
* This group may not be open to posting.
This is a safety check. Because of the dual-writing pattern, there's no reason it should be necessary, but with migrations it makes sense to be extra-cautious and to double-check your work.
We plan to share more posts on our data infrastructure: like you pointed out, there are lots of useful patterns to share. In the meantime, I’ve updated the post to be more consistent (thanks for mentioning it.)
Chris, thanks for leading the charge. We're very interested in having RethinkDB join an open-source foundation.
I've been overwhelmed (in the best way) by the level of support we've seen from the community in planning RethinkDB's next steps. If you'd like to contribute to the open-source project in any way, let us know [1]. You can also join us in #open-rethinkdb on our public Slack group, where we're starting the planning process.
Feel free to reach out to me with ideas and questions. Thanks for all the kind words.
I have to defend Compose.io here. They spent countless hours working alongside the RethinkDB team to debug problems, provide fixes, and improve the product.
We have always considered them key collaborators and contributors to the RethinkDB ecosystem. There is a conversation to be had about the difference in business models between RethinkDB and Compose.io, but I would never describe it as anything but friendly cooperation and mutual support.
I'm glad to hear that they expressed their dedication to preserving RethinkDB's open-source future. We're working to contact all the folks in our community to decide the next steps together. I'm excited to keep working with them.
Thank you for your kind words on our behalf. Hopefully the product we created together with the community will have a bright future.
Good to hear that they've contributed and that you're cool with it. It's inspiring to see that you're still putting your users first in spite of everything.
We wanted to share RethinkDB's next steps in our new home with The Linux Foundation.
We've also had a lot of folks ask if they can donate to support the project. Stripe has generously offered to match up to $25k in donations (which will help fund server costs and future development.) You can learn how to contribute to the project with OSS contributions or donations here: https://rethinkdb.com/contribute