Async Coding in Play with both Java and Scala

This meetup, Jim Brikman from LinkedIn will be giving a talk. You might have seen Jim's writing on the LinkedIn blog about their choice to use Play. (http://engineering.linkedin.com/tags/play)

Here's what Jim will be talking about:

At LinkedIn, we have started to use the Play Framework to build front-end and back-end services at massive scale. While many developers in the Java and Scala community know Play for its developer productivity benefits, one of Play's lesser known strengths is that it is built on top of Akka and Netty and natively supports non-blocking I/O (NIO).

NIO is a big win for a service oriented architecture. Under the hood, LinkedIn consists of hundreds of different types of web services running on thousands of servers, communicating with each other via remote calls. Most of these services spend most of their time waiting on responses from other services. Waiting on I/O is expensive and hard to manage in threaded servers (e.g. servlets), but efficient and easy to scale in evented servers (e.g. Play).

In this talk, I'll discuss how Play offers an escape from thread pool hell, how it opens the door to real-time web applications (e.g WebSockets), and how to write asynchronous code in Java and Scala without getting stuck in callback hell.

Here's some more info about Jim:

Yevgeniy (Jim) Brikman (http://www.linkedin.com/in/jbrikman): hacker, writer, designer, code monkey, and architect. I'm the lead developer of the project bringing the Play Framework to LinkedIn to offer developers a better, more productive way to build web services on Java and Scala. I also run the Engineering Blog, Incubator program, hackdays, and open source at LinkedIn.

See you there!