Introduce play framework from high level to code.

1. LET’S PLAY
OverView
Xuefeng.Wu 2013.07

2. AGENDA
!
Architecture
Good things
Bad things

3. M-V-C

4. PLAY

5. ROUTE
/users/1
/users/:id controller.Users.get(id:Long)

6. ACTION
request => response
object Users extends Controller {
def get(id: Long) = Action {request =>
Ok(<name>User.findById(id).name</name>)
}
}

7. OK(<NAME>PLAY</
NAME>)
Generates a ‘200 OK’ result.
text/xml
http body <name>play</name>

8. HTTP BODY
Text, Json, XML, File
Action(BodyParsers.parse.json)
{request: Request[JsValue] =>
}

9. IN ONE SLID
/users/:id
controller.Users.get(id:Long)
object Users extends Controller {
def get(id: Long) = Action{request =>
val user = User.findById(id)
Ok(Json.toJson(s””” {“name”: “${user.name}”}”””))
}
}

11. PLAY INTRODUCE
The Play Framework combines productivity and performance making it easy to build
scalable web applications with Java and Scala. !
!
Play is developer friendly with a "just hit refresh" workflow and built-in testing support. !
!
With Play, applications scale predictably due to a stateless and non-blocking
architecture. !
!
By being RESTful by default, including assets compilers, JSON & WebSocket support, !
!
Play is a perfect fit for modern web & mobile applications.

12. PLAY GOOD THINGS
The Play Framework combines productivity and performance making it
easy to build scalable web applications with Java and Scala. !
!
Play is developer friendly with a "just
hit refresh" workflow and built-in
testing support. !
!
With Play, applications scale predictably due to a stateless and non-
blocking architecture. !
!
By being RESTful by default, including assets
compilers, JSON &
WebSocket support, !
!
Play is a perfect fit for modern
web & mobile applications.

13. PRODUCTIVITY
just hit refresh v.s. restart jetty
type safe v.s. more test

14. FIX AND HIT

15. PERFORMANCE
compiled v.s. intercept
non-blocking v.s. one thread for one request

16. NON-BLOCKING
Iteratee
http://www.infoq.com/presentations/Play2

17. SCALABLE
stateless v.s. session
akka Cluster

18. SCALABLE
stateless v.s. session
akka Cluster
http://es.slideshare.net/nicmarti/play-framework-softshake-presentation

34. BUILT-IN TESTING
play.api.test.Helper._

35. ASSETS COMPILERS
CoffeeScript
LESS CSS
Google Closure Compiler
RequireJS

36. JSON
case class RegisterInfo(email: String, password:
Option[String], partnerId: Option[String])
implicit val registerInfoReads = Json.reads[RegisterInfo]
def result: BusinessResult[CreatedAccount] =
Try(request.body.validate[RegisterInfo].get) match {
case Success(registerInfo) => business.register(registerInfo)
case Failure(e) => FailedResult(invalidJson,
List(Messages("invalid.json.format")))
}

37. PLAY INTRODUCE
The Play Framework combines productivity and performance making it easy to build
scalable web applications with Java and Scala. !
!
Play is developer friendly with a "just hit refresh" workflow and built-in testing support. !
!
With Play, applications scale predictably due to a stateless and non-blocking
architecture. !
!
By being RESTful by default, including assets compilers, JSON & WebSocket support, !
!
Play is a perfect fit for
modern web
& mobile applications.

38. MODERN WEB

39. MODERN WEB
!
Designing for mobile first (even if you’re not building a
mobile app)
Build only single page apps
Create and use your own REST API
“Sex sells” applies to web apps
http://blogs.atlassian.com/2012/01/modern-principles-in-web-development/

40. ASYNC
AsyncResult
Streaming HTTP responses
Comet sockets
WebSockets

41. DOCUMENT
http://www.playframework.com/documentation

42. NOT SO GOOD
The template engine
Anorm

43. THE TEMPLATE ENGINE
lack of UI helper
reload need compiler
meaningless static
http://en.wikipedia.org/wiki/Template_engine_(web)

44. ANORM
write SQL by hand
less transaction management

45. REAL TIME

46. Q&A