It worked for Twitter! Seriously though: scala is much much more pleasant. And scala has a great story for using Java libs. And since spark is kind of framework-y (use its scripts to submit, start up repl, etc) the projects tend to be lead projects, so even in a big company that uses Java the cost of scala is low and fairly isolated. If you need to write large amounts of supporting libraries, you are free to use Java or scala as you see fit.
El martes, 8 de septiembre de 2015, Bryan Jeffrey <bryan.jeff...@gmail.com> escribió: > All, > > We're looking at language choice in developing a simple streaming > processing application in spark. We've got a small set of example code > built in Scala. Articles like the following: > http://www.bigdatatidbits.cc/2015/02/navigating-from-scala-to-spark-for.html > would seem to indicate that Scala is great for use in distributed > programming (including Spark). However, there is a large group of folks > that seem to feel that interoperability with other Java libraries is much > to be desired, and that the cost of learning (yet another) language is > quite high. > > Has anyone looked at Scala for Spark dev in an enterprise environment? > What was the outcome? > > Regards, > > Bryan Jeffrey >
