Hello! Michael Drogalis, the developer, here.
I talked a little bit about why I wrote Onyx on the Clojure mailing list: https://groups.google.com/d/msg/clojure/OmHzAEfYe9U/33e0a0l3...
It's mostly driven by the need to use data structures in places where I didn't have them - I only had things like macros and functional composition.
Re:Internal Design of Onyx
by sixdimensional on Thursday October 09, 2014 @05:39PM
(#8435150)
Thanks for the info, and awesome work on Onyx!
Re:Internal Design of Onyx
by sixdimensional on Thursday October 09, 2014 @01:42PM
(#8433921)
More information for those interested from the developer's tumblr: http://michaeldrogalis.tumblr.com/post/98378329045/onyx-a-ne...
It seems this is the current popular technique (and rising in popularity) to solving some really long-standing, hard, data processing problems and related performance concerns - really an extension beyond the progress we made with distributed MapReduce algorithms and the like in Hadoop.
There are certainly a lot of implementations coming out - why would one choose Onyx over say, something like Spark? Is it just the compatibility with the Clojure programming language and the associated, implied benefits of functional programming paradigms (among others?).