RethinkDB 1.12: simplified map/reduce, ARM port, new caching infrastructure

Re:RethinkDB 1.12: simplified map/reduce, ARM port, new cach... by dataminded on Wednesday March 26, 2014 @09:33PM (#7477986)

Background: I've done a fair bit of hiring for analysts and have worked in most facets of analytics/DW including vendor evaluation/selection and implementation.

I think that the lack of a SQL interface is a big negative. It's really hard to find analyst (not programmers) with good technical skills or train them to proficiency in new technologies. I would have a very hard time selling a platform that existing analysts wouldn't be able to use right away and that few people on the market could work with.

Also, designing a new language makes integration with other applications that much harder.

[ Parent | on HN ]

Re:RethinkDB 1.12: simplified map/reduce, ARM port, new cach... by coffeemug on Wednesday March 26, 2014 @10:44PM (#7478259)

That's a great point. Our hypothesis is that great querying capabilities for analysts and great querying capabilities for programmers should look completely different, and be two totally different technologies. We'll eventually ship a solution for analysts, but I don't think a great database product should shoot for a lowest common denominator.

[ Parent | on HN ]

Re:RethinkDB 1.12: simplified map/reduce, ARM port, new cach... by nXqd on Wednesday March 26, 2014 @10:17PM (#7478156)

You can find the answer to this in coffeemug' post :

"We're assuming people will be using ReQL fifteen years from now."

[ Parent | on HN ]