Please log in to watch this conference skillscast.
We've heard how Twitter and LinkedIn adopted Scala on greenfield initiatives and we're excited to use a more expressive language running on a robust, familiar VM. But is the ecosystem ready to support the demands of a long-established enterprise infrastructure, mission-critical (non-Scala!) middleware and the traditional dev-test-release workflow?
We'll start by exposing what drove our decision to dive into Scala. Next: We'll talk about some of the challenges we faced designing, building, load testing and debugging our service. We will discuss some of the patterns we used moving to a more reactive platform, the availability/maturity of the tooling and some of the framework code we had to write. Finally we'll outline the benefits gained through embarking on this project and any prices we have paid for doing so.
YOU MAY ALSO LIKE:
Scala does the catwalk
Ariel is part of the Labs Team of Net-A-Porter. After a long lasting happy romance with Java, he is starting to share the love with other JVM running languages as Scala.
Initially joining Net-A-Porter as a Java Developer, Ian has spent the last two years developing with Scala for the Labs Team. This transition has led him to author two open source scala projects and contribute to others such as Spray and json4s.