E-Books

Play for Scala

by Peter Hilton, Erik Bakker, and Francisco Canedo

Play for Scala shows you how to build Scala-based web applications using the Play 2 framework. This book starts by introducing Play through a comprehensive overview example. Then, you'll look at each facet of a typical Play application bothby exploring simple code snippets and by adding to a larger running example. Alongthe way, you'll deepen your knowledge of Scala as a programming language andwork with tools like Akka.

Play is a Scala web framework with built-in advantages: Scala's strong type system helps deliver bug-free code, and the Akka framework helps achieve hassle-free concurrency and peak performance. Play builds on the web's stateless nature for excellent scalability, and because it is event-based and nonblocking, you'll find it to be great for near real-time applications.

Play for Scala teaches you to build Scala-based web applications using Play 2. It gets you going with a comprehensive overview example. It then explores each facet of a typical Play application by walking through sample code snippets and adding features to a running example. Along the way, you'll deepen your knowledge of Scala and learn to work with tools like Akka.

Written for readers familiar with Scala and web-based application architectures. No knowledge of Play is assumed.

The free sample PDF available here includes chapters 2 and 8. All registrants qualify for a Typesafe discount and will save 45% off the price of the full Play for Scala book (all formats) as it becomes available by referencing promotional code tspfs. If you are interested in purchasing the full book get it here. Offer only valid at manning.com.

Please enter your information to receive your E-book copy of a subset of Play for Scala by Peter Hilton, Erik Bakker, and Francisco Canedo and be signed up for the Typesafe Newsletter. Once you've entered your information and submitted the form, the PDF will be emailed to your address.

From the blog

While Reactive application development is off to a roaring start and becoming mainstream, this leads to demands on Operations that are simply not met by yesterday’s software architectures and technologies. The pressure facing enterprises to manage resilient, responsive systems is brutal, yet most existing technologies available today are not designed to deploy and manage Reactive systems running on clusters. It’s due to this fact that Operations face a higher risk of downtime by using inappropriate tools/practices at a time when being unavailable is more costly than ever. So why is this happening? Well, it's not 2005 anymore–and why that's a problem for Operations is explained here...

Ten months ago we posted about architectural changes to Typesafe Activator. After a few a lot of yak shaves, side projects, and detours, we have Activator 1.3.0 based on sbt server, a new setup where multiple clients can share the same instance of sbt. sbt server is also available in ABI-stable protocol-stable form for other clients (IDEs, command line, desktop status icon, whatever you can think of) to try out.