Spark 2.0 introduces a new mode of computation for Spark, Structured Streaming. This post gives a very basic fully working example of using Structured Streaming. The full code is available here on github.

This is the second part of a series of posts looking at how features in Java 8 can help Scala developers stick to a functional style if they find themselves needing to develop Java code. The first part was about handling immutability.

Early on in my experience programming with Akka, I came across the post “Attention: Seq Is Not Immutable”. From that point on, I’ve always been careful to use scala.collection.immutable.Seq rather than scala.collection.Seq when designing messages to pass between actors, and in general to ensure messages are immutable.

Scala Macros have been part of the language since Scala 2.10. Let’s have some fun with them…

Like many Scala developers I was developing object oriented, imperative code in Java long before switching to Scala and learning the techniques of functional programming. In the meantime, Java 8 has come along with some enhancements to make functional programming in Java more natural. So as a Scala developer, if required to switch back to Java, what can be done to maintain a functional style?