Content deleted Content added
m No lang → <pre> |
Summary pane on right side states Cuneiform is implemented in Erlang, which means it runs on an Erlang Virtual Machine (BEAM), and added this important fact to be searchable. I am a Sr. Developer and know this. See Erlang page if questions. |
||
Line 38:
| url = http://ceur-ws.org/Vol-1330/paper-03.pdf
}}</ref>
It is a workflow [[Domain-specific language|DSL]] in the form of a [[Functional programming|functional programming language]] promoting parallelizable [[algorithmic skeleton]]s. External tools and libraries, in, e.g., [[R (programming language)|R]] or [[Python (programming language)|Python]], can be integrated via a [[foreign function interface]]. Cuneiform's data-driven evaluation model and integration of external software originate in scientific workflow languages like [[Apache Taverna|Taverna]], [[KNIME]], or [[Galaxy (computational biology)|Galaxy]] while its algorithmic skeletons ([[Higher-order function|second-order functions]]) for parallel execution originate in data-parallel programming models like [[MapReduce]] or [[Pig (programming tool)|Pig Latin]]. Cuneiform is implemented in Erlang, and therefore must run on an Erlang Virtual Machine (BEAM) similar to the way Java must run on a JVM (Java Virtual Machine). Cuneiform scripts can be executed on top of [[Apache Hadoop|Hadoop]].<ref>http://www.saasfee.io</ref><ref>{{cite web|title=Scalable Multi-Language Data Analysis on Beam: The Cuneiform Experience by Jörgen Brandt|url=http://beta.erlangcentral.org/videos/scalable-multi-language-data-analysis-on-beam-the-cuneiform-experience-by-jorgen-brandt/#.WBLlE2hNzIU|website=Erlang Central|accessdate=28 October 2016}}</ref><ref>
{{Cite journal
| last1 = Bux | first1 = Marc
| |||