RethinkDB is one of the developer tools that we at Stripe most looked up to.[1] The team had so many good ideas and rigorous, creative thoughts around what a database could be and how it should work. I'm really bummed that it didn't work out for them and have enormous respect for the tenacity of their effort.<p>I'm also excited to have them join us here at Stripe. As we've gotten to know Mike, Slava, and the other Rethinks -- and shared some of our plans with them and gotten their feedback -- we've become pretty convinced that we can build some excellent products together in the future. I'm looking forward to learning from all of them.<p>[1] (And, for me, even before Stripe -- I started learning Haskell with Slava's Lisp-interpreter-in-Haskell tutorial back in 2006... <a href="http://www.defmacro.org/ramblings/lisp-in-haskell.html" rel="nofollow">http://www.defmacro.org/ramblings/lisp-in-haskell.html</a>)
Why does nobody seem to have any introspection on why RethinkDB failed? Clearly there are some major problems that people re ignoring. If my favorite DB (I must mention Kx Systems once a month) folded, I could give you a laundry list of issues where things went sideways, but all I see is glowing praise and comments about the best tech not always winning (KDB knocks the socks off of everything, but I sure can give you a list of places it fails).<p>This isn't meant to be harsh, but these are times to learn, not simply pat each other on the back.
It seems that unfortunately RethinkDB the company was architected in such a way that the success of their product, in terms of performance and developer experience, led to a decrease in revenue.<p>This shutdown therefore goes a long way to say how talented and ethically correct the team was, something extremely evident in how they put correctness and reliability in front of performance.<p>In short, RethinkDB is a very solid piece of software that does well where (many) other NoSQLs fall short, that is:<p><pre><code> * easy HA and automatic failover
* easy auto sharding
* rational query language
* ease of administration and awareness (webUI)
* realtime capabilities
* perform well on the Jepsen test!
</code></pre>
Now, what could have they done differently to stay afloat?
What avenues do we have to fund fund such great projects, whose <i>point</i> is being OSS?
(I mean, one of the selling points of RethinkDB is that one can trust it in this land of NoSQLs that promise but don't deliver, and this is in part thanks to their open development processes)
I just want to personally thank Slava for his exceptional work over the past few years - at every step him and his team have been classy and professional, and brought real creativity and intelligence to the world of databases and startups.<p>Its clear to me that Rethink is the model for future databases - its just that DBs have a long gestation as no-one wants to risk their data until the code is aged like a fine wine. Its an important longterm technology play - just the kind we need to improve things for all of us.<p>In two or three years I think they would be making money, I think this is a failure of capitalism or imagination our HN/SV community.<p>To those several of us who have the power to write a check, please consider doing so, Rethink have been relentlessly building the future [ and you will make money ]
Wow. I was seriously rooting for them. I'm looking forward to Slava's posts about their challenges on the business side. There's a part of me that's angry that MongoDB - which some would say has made an objectively worse product - has succeeded.<p>My initial thought is that MongoDB has done a way, way better job at SEO. The number of blog posts about RethinkDB pales in comparison to Mongo. I wonder if they got beat on sales as well? Not sure.
I hope this isn't true. Having worked at/on multiple competitors I have nothing but respect and admiration for the work the RethinkDB team has done to make a great database and development platform.<p>This was real technology! I'm truly sad that the environment is such that great work like this can't continue to be funded.<p>Thanks for showing everyone how to write amazing documentation, caring about the fundamentals, and for the incrediblly snazzy admin panel.
Very sad to hear, but hopefully the software will continue to be developed in an open source format.<p>Keep this in mind when you invest in a certain technology: some organizations, especially nonprofits (for example, the Apache Software Foundation, Python Software Foundation, the new Node Foundation) are probably going to support and develop their software for extended periods of time relative to, say, a startup or for-profit (Parse, MongoDB and RethinkDB immediately come to mind).
This is honestly quite depressing for me to hear. I've always liked the team and the fantastic product they created. A couple of years ago, when I was working on a DB product myself, I met a few of their team and I was just blown away by how nice and welcoming they were, even to someone developing a product that could potentially compete with theirs.<p>Later onwards, when I was working on an NLP startup earlier this year, I opted to use RethinkDB because I had seen how clean, smooth, and fast its internals were. When I had a hiccup with running a cluster in here cloud and tweeted about it, Mike and others from. The RethinkDB team instantly reached out to me and helped me resolve the issue.
Really sad to hear this. I always had a ton of respect for you guys and your commitment to solid technology. (I mean y'all even passed Aphyr's Jepsen tests out of the gate [1]) You've also always paid a great deal of attention to interface, both in your query language and in administration.<p>One of your engineers even wrote once that maybe you took longer than you should have and over-engineered some things, but now that that was in place y'all would be better off for it. I'm sorry that didn't wind up being the case, at least as far as your company is concerned.<p>RethinkDB was at the top of my list of technologies I want to build something on. I even went to your (one?) meetup in Boulder. I guess my t-shirt is now a collectable :-/<p>But I'm happy for y'all that you wound up finding a great place you can all work together. Best of luck!<p>[1] <a href="https://aphyr.com/posts/329-jepsen-rethinkdb-2-1-5" rel="nofollow">https://aphyr.com/posts/329-jepsen-rethinkdb-2-1-5</a>
Just started a new project at my company using RethinkDB, very early stages, but I was amazed at how well this was documented and implemented. Coming from different ORMs to use with MongoDB, ReQL was a joy to work with and I didn't even want to use an ORM(for me at least, others may disagree).<p>Sad day to me, but as an open source tech, I hope and trust it will continue to live on.<p>It sounds like the company landed at Stripe. Good for them. Glad they weren't left out in the cold.<p>Thank you all very much for your hard work. In my short period of time I have had using RethinkDB, it's been a pleasure to work with.
I'm very upset to hear this. RethinkDB, and the team behind it, have been inspirational to me and it has transformed my day to day development workflow. Their dedication to developer experience (amazing docs, ReQL, admin tool,...) has been something I've particularly admired. I'm relieved that the team has a new home though and it's fantastic that a company that has similar traits is the destination - props to Stripe and the RethinkDB management team for making this happen.<p>I hope to see RethinkDB to live on in the OS community.
I used Slava's blog to learn about Lisp and went on to build a product with Weblocks, which was a continuations-based web framework that Slava created back in the day (I only recently finally deleted a forgotten 8-year old todo about merging in my refactored Weblocks formview). Random trivia (kind of) - the syntax and concepts in Weblocks actually bear some resemblance to Goat, which is a framework that Patrick had created and used to build the original version of the Stripe dashboard (likely just because both of them come from a Lisp-heavy background).<p>I had just started a new company using RethinkDB, and it was definitely poised to be my go to database for new projects. Anyway, all this is to say, for someone who I know only through his works, I have great respect for Slava and want to thank him for the work he's done. Here's to hoping that RethinkDB finds a way to continue.
Slava is one of the smartest people I've met (and I'm sure the rest of the team follows suite) - it's indeed sad that the RethinkDB company is no more.<p>I feel we're at a stage where some of the key technologies/platforms are coming out of relatively small companies (docker, storm, rethinkdb, to name a few), however, it appears it can be tough to make a business out of this alone.<p>I'm consequently very happy to see that the RethinkDB team have found a home at Stripe and hope that works as a setup to allow the talent to flourish and keep producing great work/innovations.
This is very sad. RethinkDB is my favourite database engine of all time.<p>I have huge respect for the RethinkDB team - They've put the product above everything else and they've made it accessible to as many developers as possible by making it open source.<p>I think that in spite of this announcement, I will likely continue to use RethinkDB.
I recognize there's hundreds of different factors that played a role in the story of RethinkDB and its relatively poor adoption. I'd like to touch on one specific point (probably far from the most important one) - the name.<p>I think you guys introduced friction <i>very</i> early on with some of the developers, because of your name. Given the context of our times where many of the devs joke around about "yet another 'revolutionary' database that claims to be different and then does the same thing, but dropping some crucial functionality" (for which I primarily blame MongoDB), "RethinkDB" can be considered a bit of a sardonic name. It can also read as "we need to reject the notions other databases are built on and rethink it all", which to more conservative devs can feel as an attack on decades of thought and design around their beloved MySQL and PostgreSQL.<p>Basically, I think this name might actively discourage developers from adopting your db or at least playing around with it.
Per Crunchbase:<p><pre><code> Dec, 2013 $8M / Series A2
Sep, 2011 $3M / Series A
Apr, 2010 $1.2M / Seed
Jun, 2009 undisclosed amount / Seed
</code></pre>
Did the company have any revenue or was that the only money the company had to run on?<p>Assuming that info is correct, that's pretty slim for building a "hard tech" type of company. Building a database (from scratch no less) is a lot of up front work. Even after it's built you need to convince tech people to want to use it, convince their bosses to let them use it, and even then, hire sales people to sell support contracts.
If RethinkDB is really better than Mongo then where is the blog post about it?<p>Where are all the scaffolding tools? The examples?<p>I have only heard of Rethink because I read HN every day. But no one knows about it. That is obviously the reason it failed - bad marketing.
RethinkDB was simply too good to be true. I've been reading Slavas defmacro.org probably since he started writing it, and was watching where he will end up. It was no disappointment that he created this with his cofounders, and while I'm a bit sad they couldn't find a viable business I know they are young and ambitions, we will hear from them.<p>Go Slava!
For people mourning the loss of rethinkDB, and who are interested in alternative document based NoSQL DBs under development, please checkout ArangoDB. It's my favorite NoSQL database. I have no affiliation with them.<p>Beautiful query language called AQL, and graphing support (multi-model) baked in.
Does anyone have experience with Postgres' pubsub[1] as a means for realtime apps?<p>1. <a href="https://www.postgresql.org/docs/9.6/static/sql-notify.html" rel="nofollow">https://www.postgresql.org/docs/9.6/static/sql-notify.html</a>
Rethinkdb is great software that was really designed with technological goals, one after the other, in mind. I'm a bit surprised to see the company shutting down. I mean, in some way, it's years they work at the project, but in the final usable form the project is not so old after all... Anyway to make it viable for the project to have a good live as an OSS project, there is to build a big community of core developers, and that's hard, so as a first step what I would do to ensure the viability is to strip-down it as much as possible in order to reduce the codebase of the fundamental part of RethinkDB to a more manageable size/complexity.
Holy shit, my worst nightmare is realized. I LOVE RethinkDB, I use it for EVERYTHING. It has everything I've ever wanted in a database. Relational documents, realtime feeds. Sadness. Someone better be picking up from where they left off.
Interesting, I expected ArangoDB close shop before RethinkDB.<p>I found both nice and even built a product on top of rethink over the last twelve months. Guess I was blended by the hype :D
Mike has been one of the most genuine and helpful people I've met - always offering to lend an ear or offer suggestions and feedback. It must be really difficult to stop doing something that's been such a core part of your effort and thoughts for so long. I hope you and the team find interesting and engaging things to work on.
Very sad to know that RethinkDB is shutting down. This was one company that I wanted to see being successful! A great tech team taking on a hard technical problem. Even if they are closing down, I hope they have changed the landscape.<p>Also having followed Slava for a sometime, nothing but respect and admiration for him!
RethinkDB advanced database technology. Congratulations on a good run. Like many things, we may not realize the impact of their work today, but with the product going open source, it can serve as both a learning tool/inspiration for new platforms in the future, as well something to build on. I imagine the product will take its place in the halls of database history, even if it didn't succeed in the market financially. This is a legacy to be proud of, and glad to see the team has somewhere awesome to go!
A while ago, I heard how good RethinkDB is and tried to check it out and found this page.<p><a href="https://rethinkdb.com/docs/sql-to-reql/javascript/" rel="nofollow">https://rethinkdb.com/docs/sql-to-reql/javascript/</a><p>The more complex the query becomes I just felt everything was getting less intuitive compared to the SQL version and ended up not actually using it.<p>For anyone who switched from SQL, I'd like to know how it felt to write RethinkDB queries. Did they start to feel fluent later on?
I would be very interested hearing @coffeemug's views on the tension between building a business and building an open source product. (Those I know who have done this range from "never again" to "lost a fortune in sales")
I wish RethinkDB had published a performance benchmark against Hadoop. It'd be enough to show the world how ahead of its times RethinkDB is.<p>I also wish I knew what RethinkDB's investors are thinking.
I think I'm gonna try and teach myself to work on this in its new open source incarnation, because I was rooting for it hard while it was still a company, but it was perpetually in a state of "soon, not yet", and now "not yet" is never unless the people who want it step up.
Bummer. Had Rethink in my list of things to eventually tinker-with. Is it stable where it should still be considered as a viable choice for your tech stack, or is this pretty much a deal-breaker?
This is sad - Was planning on moving from Postgres to Rethink as our plan once we start to hit scalability limits / needing to shard. I guess we will see how the open source efforts go.
While RethinkDB looks amazing I'm glad I didn't listen to the people here demanding me to switch from MongoDB. In the future I will just stick with what works.
Their chance of surviving would have increased dramatically if users could install rethinkdb as addon on Heroku.<p>Availability as a service was an issue, the compose deal did not work well for me, as my stuff was hosted on heroku.<p>Anyway, rethinkdb is probably the most awesome database I've tried.<p><a href="https://github.com/birkir/react-starter-kit-rdb" rel="nofollow">https://github.com/birkir/react-starter-kit-rdb</a>
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.<p>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 ...
As a former employee at Rethink, I'm super sad to hear about this, but know that they are all great people capable of even more than what they have accomplished with this amazing database! Will continue to recommend RethinkDB ferociously to everyone I know and will always fondly look back at my time there!
Never used RethinkDB, but this is the first time I've seen an announcement this written as "we are shutting down, the team is moving to Stripe" rather than "We've been acquired by Stripe! Nothing will change except our product will stop working in 30 days"<p>Much respect for the no-BS announcement.
RethinkDB is an amazing product. I've had the pleasure of using it a few times in my projects and the experience has always been very smooth. I would recommend RethinkDB to anyone, and you guys should be very proud of your work.<p>I'm sad that all that excellent engineering hasn't translated into a profitable business model. Part of me wants to suggest you make a donation campaign, and I'd be happy to become a regular donor. But it's understandable and respectable that you guys want to move on to other ventures.<p>I've also used Stripe's API and their systems are also very good. I'm glad to hear you'll find a place with another solid engineering team and I wish you guys all the best.
This is very sad to hear this looked like a real product.<p>Quite off-topic but has anyone managed to implement something similar to Changefeeds in MongoDB? RethinkDB sends both old data and new data and watching the oplog sounds like a bad idea.
I have tinkered with RethinkDB a lot recently. It's the NoSQL DB (and the DB of any kind, I believe) that has the deepest focus on real-time features, that mixed up with Golang's concurrent model can support really powerful and highly scalable real-time apps.<p>But my question is, what are your thoughts on building more than a product but a business with RethinkDB? Will the support quality decrease? Will Stripe offer architectural consulting? Will developers be interested in learning ReQL?
Since our startup is build entirely on Tornado + RethinkDB + Emberjs + Python , this is a huge blow.<p>But i do not worry , since this is announced many folks willing to support from community and many willing to contribute to RethinkDB in terms of both profit sharing and code steps up.<p>Also Stripe and Compose.io step up , to stand with RethinkDB .<p>I for one , a Startup Enterprenuer and Founder of Software Agency from Myanmar , Promise to share at least 5% of our profit on projects developed using RethinkDB to keep it Running .
It is sad to see that making a living from development tools is becoming less and less an option.<p>Kudos to the RethinkDB team for trying, and giving us a very useful DB.
I'm sad for this. I really liked rethinkdb and thought the potential for future development seemed really promising. They seemed to really know how to ship -- it's sad to imagine the momentum they had created fizzling out ... i would've liked to have seen what they would have came up with over the next couple of years ...
Really sorry to hear it Slava. You guys were doing great work. At the end of the day, I think that open source has really killed pure database companies aside from the incumbents. We'll see where MongoDB ends up but they have the advantage that a support contract business model works when your product needs support.
I've been working on a Clojure RethinkDB driver for about a year now, and I've always been incredibly impressed with the Rethink team. Their openness, friendliness, and helpfulness when asking questions has always been outstanding. You'll be sorely missed all.
I never used it in production (lack of need, not a lack of interest), but I always enjoyed playing with RethinkDB. Really fantastic work - both under the hood and the presentation on top. Be proud of the work everyone did. Stripe is a great home to end up at!
This is sad. Looking forward to the post-mortems. A question in the interim: Did rethink ever consider building a SaaS business around the product? What were the reasons against it? Were there (a lot of) customers asking for a hosted version?
Wow, I've always used RethinkDB for toy DB stuff here and there, but nothing serious. I loved how well everything was put together, from the documentation to the homepage. Hopefully the project can live with OSS contributions.
Core tech products are hard to sell. With so many passengers on big data boat - MemSQL / VoltDB / Postgres / DataStax / DataBricks / Cloudera / Horton many more.<p>Your sales force strength becomes critical.<p>Waiting for insider insights.
I find it hard to trust HN users as I was about to adopt and migrate from MongoDB to rethinkDB based on consensus by HN user comments about it being undeniably superior, yet it was actually close to shutting down apparently.
Just wanted to say good luck with everything to the team, and especially to neumino - you've personally helped me years ago on freenode writing some long ReQL queries when I first started experimenting with Rethink. :)
I don't know what to think. I am angry and sad that my favorite db is going away?! On the other hand, I am trying to understand and be supportive of the team behind it, as I have huge respect for them and their work.
Ive been teaching my siblings programming. It took them literally a day to learn rethinkDB.<p>That should say a lot about how amazing RethinkDB is. It's unfortunate to see this get shut down as RethinkDB is pretty easy to work with
Looking forward to the more detailed writeups since I'd love to read why it wasn't possible to build a sustainable company around such an excellent product.<p>Good move by Stripe to pick up these fantastic engineers.
Massive bummer - Slava and Mike and the team were super top-notch. RethinkDB will always be my goto to explain the delta between a great and a poor first experience for any dev tool.
Looking at their website, they are being used be:
* Nasa
* Jive
* wise.io, mediafly etc<p>Just another confirmation that many of those companies list all these big well-known 'customers'.. except they are just lying. Maybe someone in nasa downloaded rethinkdb once and they just listed them there?
My greatest condolences to you guys. I have met with Slava a couple times, and with Mike several. They are incredibly down to earth and I felt they were very important to contributing to the democratization and humanization of databases (an otherwise unfortunately very vicious and elitist industry).<p>So what is next? I need to strongly remind people that both Mozilla Firefox and Blender were Open Source projects that survived their parent companies. This is not a death statement, and very easily could be a rebirth of Rethink.<p>Despite working on a competing database, I want to take a moment to explain why RethinkDB is the best in its chosen niche, by comparing it to other options out there:<p>- MongoDB. You won't get realtime updates and relational documents if you use MongoDB compared to RethinkDB.<p>- MySQL/Postgres. Rethink's awesome ReQL query language is a joy to work with compared to standard SQL. Without Rethink, you'll be missing document storage and live queries.<p>- gunDB. Our model is Master-Master, which while we think is great, it fundamentally restricts you from building Strongly Consistent systems, like banking apps, etc. RethinkDB is the only realtime updating Master-Slave system out there. They clearly win here.<p>- Redis. RethinkDB still has amazing speed and performance, but offers so much more than Redis by itself can.<p>- Hadoop. I know less here, but I've heard that RethinkDB has an amazing query optimization engine. Automatically taking your query and sharding it out across the distributed storage system.<p>RethinkDB is a winner in these technical aspects and fits for a very well defined problem. I encourage people to still use it and contribute to it if their business matches that. Don't let news like this deter you, or else we would have lost gems like FireFox and Blender.<p>Best regards to you guys, you are awesome.
Haven't played with it, but everyone about RethinkDB looks positive. Hopefully it will continue to develop in the open source community.<p>There are so many projects that really need attention to keep open source growing. I started looking at what I could do for IRCv3 projects recently because I'd really like to support an open source alternative to Slack.
How long have the Mets fans been doing that hammer cheer?<p>Because it looks eerily similar to another arm swinging chant that another NL East team does.
People saying they "failed" -- I disagree. It is VERY hard to sell products that are essentially free. Its largely down network effects and luck or having an _in_ with the good old' boys network. Its not more popular than every other db..so what.. And the best systems are rarely the most popular. Btw popularity is not merit.<p>But they made a badass database that relatively speaking IS very popular. So thats not failing. Thats winning.<p>Also maybe these people are being more honest and responsible than some startups that keep flushing millions knowing they are unlikely to ever have a positive cash flow.<p>Plus getting acquired by some company like Stripe, realistically, whether there was some big exit or not, is the dream of many people.<p>So given the reality of the startup scene to say they 'failed' is a joke.