We are very excited to reveal what we have been working on for the past months: together with our partners we have developed a draft specification for Reactive Streams, and matching that we have created a draft implementation of this upcoming standard. The code is available on github and we have prepared an Activator template to get you started—for now only using Scala, but a Java version will be forthcoming shortly.
See also the official announcement on the Typesafe blog.
In the post “The end of ORM” Pere Villega presents a practical engineering view on why Event Sourcing is a much better fit for persisting an object’s state than mapping it into a relational database.
Report from Vienna Scala User Group.
Impressive – I didn’t think that we would actually get a solution that was so good, in such a short time! In just three hours our 26 participants implemented a cluster with Akka, and an evolutionary algorithm on top of it.
Writing concurrent programs is hard. Having to deal with threads, locks, race conditions, and so on is highly error-prone and can lead to code that is difficult to read, test, and maintain. So does this mean you have no choice but to journey deep into the bowels of threads, locks, and race conditions in order to build a concurrent application? Thanks to frameworks like Akka, the answer is no. The post referenced below introduces Akka and explores the ways in which it facilitates and simplifies the implementation of concurrent, distributed applications. Includes code samples.
Concurrency and Fault Tolerance Made Easy: An Intro to Akka
(submitted by H. Singer)