ddrum001

I suppose those who only write in relatively similar languages like JS, Python, and Ruby start seeing all the tiny differences and miss the entire subset of Lisp languages that offer so much more.

I guess technically there's no guarantee that your username automatically gets the page without "/user/", but it's still shady.

I think this project approach is excellent - this seems to map much better to real experience in a job.

The features they include are nice, but it would be really helpful to have dependency support for languages Scala and Java like IntelliJ does.

Yep, that's the first thing that came to mind for me too - not sure why they chose to keep it.

Interesting I suppose, but doesn't this select for candidates that can parse through code that doesn't self document?

I don't think you have a choice, you'll have to use MapReduce if the data is too big to fit into memory. I believe that's what Facebook and Google do:

https://www.facebook.com/notes/facebook-engineering/scaling-...

http://googleresearch.blogspot.com/2009/06/large-scale-graph...

I never considered Clojure for design, thanks for sharing!

That's a great point for our next session - Summingbird would be perfect for everyone trying to implement Lambda Architecture without having to produce separate code for streaming and batch.

Great post, would love to see RethinkDB with horizontal scalability in future releases.

You're correct that it's very difficult to balance between giving an overview and over-simplifying. We intended this to be a starting point, knowing that we'd have to make a trade-off between including more details and giving a concise overview.

For NoSQL specifically, it's difficult to put every database in only a few categories. We discussed that Cassandra and HBase are "maps of maps" in the details, and we definitely didn't want to imply that they have the same model or use-cases as Redshift. Perhaps our next iteration will explain the "column family" more and include a separate category for the databases that were inspired by the Big Table data model.

Thanks, if you mouse-over the databases box, you'll see Redshift under Columnar - we do see a lot of Netezza and Aster as well.

Thanks, we'll definitely include links in our next iteration.

Thanks, if you mouse-over the Batch and Database, you'll see more categories. Presto is under Batch SQL and Elasticsearch is under Document Oriented.

We see Flume, Solr, and Impala a lot but decided to omit them to strike a balance between including more technologies and overwhelming people who are new to the field. Inevitably, we had to leave off many of our favorite technologies.