Earlier quoted context omitted.
That's the salary of a single employee. Surely they can afford a database on the payroll.
please do introduce me to your generous VC. At current low interest rates, building a stack that is reliant on KDB, will cause a large valuation hit because you're effectively locked into a negative -250k/year cashflow in perpetuity. At a 5% discount rate for example that's more than 5m USD of inflexible negative NPV right up front. Look there are fintech applications where this will be seen as fine (right tool for t…
RethinkDB is shutting down
231–240 of 457 posts
Re: RethinkDB is shutting down
#232Re: RethinkDB is shutting down
#233RethinkDB 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. I'm also excited to have them join us here at Stripe. As we've gotten to know Mike, Slava, and the other Reth…
I secretly (not 'secret' anymore I guess) and irrationally trust Stripe to do good on RethinkDB. Also, TIL: Slava is defmarco. Yeah defmarco, that's how I read it for a long time. I especially love this piece from defmarco http://www.defmacro.org/ramblings/fp.html
Re: RethinkDB is shutting down
#234A while ago, I heard how good RethinkDB is and tried to check it out and found this page. https://rethinkdb.com/docs/sql-to-reql/javascript/ 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. 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?
Re: RethinkDB is shutting down
#235A while ago, I heard how good RethinkDB is and tried to check it out and found this page. https://rethinkdb.com/docs/sql-to-reql/javascript/ 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. 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?
It took a few weeks for ReQL to really sink in, but once it did, I much preferred it to SQL. As my sibling comment says, its very linear: do this then this then this then this. It also feels very much like sequence processing in functional languages (and I was using Clojure at the time, so it really meshed very well).
I also found it much easier (than SQL, at least in my limited experience) to reason about performance because I knew what it was doing. Is this looked up by index? Yes, because that's the command I used.
So, yeah, ReQL actually ended up being one of the things I liked most about RethinkDB.
Re: RethinkDB is shutting down
#236Earlier quoted context omitted.
Well, to each his own, but I don't think the product was the problem. Lots of people love RethinkDB. The comments here are proof of that.
This is the exact kind of comment I was warning against. The "it surely can't be the technology!" comment when yes, Shirley, it really can be. Even the best database systems I know (orders of magnitude quantitatively better than RethinkDB) have areas of technical weakness. And not just some areas, but usual gaping valleys. Nothing does everything well, and if it tries to it usually does everything below average. Time…
Literally no users, and almost no employees at the vendors, I would bet (if my experience is not unique) have any idea of the qualities of the software they use/peddle, its semantics or guarantees, or its performance characteristics or how to use it correctly.
This makes the technology secondary; what is most important is how well you carve out mindshare. Whether that is even primarily down to "good" marketing is something I doubt. In the modern saturated database market, it is entirely unclear to me how you win sufficient mindshare and trust to obtain a wide enough (paying) userbase.
I have no idea if RethinkDB was "good" or not, as I did not take the time to investigate; I have little interest in "document stores". It actually seemed to me they had some pretty solid engineering foundations; the kind of thing that the industry should value highly, but due to poor information is unable to price into their purchasing decision, and as a result is missing in many modern (especially OSS) database offerings today.
Re: RethinkDB is shutting down
#237Earlier quoted context omitted.
I've always found that to be a perverse incentive model. I don't know how to do any better though. Maybe shaming companies that use OS projects heavily into donating? Not really sure how to scale that either.
I currently pay someone else to host a rethinkdb cluster. I'd rather pay rethinkdb.com to do that, but they didn't offer. I am sure they considered it and figured it wasn't a good model for them. It is unfortunate that I have (with much pleasure) used rethinkdb in several projects, yet haven't had a chance to pay them for a service that would be useful to me.
Re: RethinkDB is shutting down
#238Wow. 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. 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…
Re: RethinkDB is shutting down
#239Earlier quoted context omitted.
I'm genuinely surprised at the number of people who vetted RethinkDB and are now really concerned with this news. With the number of solutions out there to accomplish the same or more RethinkDB almost seems like a novelty choice. Surely the decision to make it business critical came with the understanding and acceptance that the company might go bust? I'm not sure what was accomplishable with RethinkDB that wasn't wi…
RethinkDB really managed to build quite a lot of positive feelings in me on the back of not very much technology. But what technology was there seemed very robust. Just kind of incomplete. My situation was very similar to latch's above. I vetted it earlier this year, after having developed warm fuzzy feelings for it last year at another company. We wound up going with Postgres + Solr because A) we've used them before…
Re: RethinkDB is shutting down
#240Interesting, I expected ArangoDB close shop before RethinkDB. 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