Outline - nraychaudhuri/play-recipes GitHub Wiki

Setting priorities: 5 is best, 1 is worst. First rating is by Chad and the second one is Nilanjan

Organizing Your Work

Must haves

  • Action composition - 5 5
  • Add local and 3rd party dependencies - 5 5
  • Adding support for new assets - 5 5
  • Filters - 5 5
  • Gracefully handling of missing actions - 5 5
  • Async action - 5 5
  • Working with cookies - 5 5
  • Remote debugging play application - 5 5
  • Using forms - 5 5

Maybes

  • Using play-navigator for programmable routes - 4 5
  • Play reverse routing - 5 3
  • Caching - 4 3
  • Passing properties to play command - 4 5
  • Using private maven repo - 3 5
  • multi module project - 2 5

We will probably have no time for these

  • Running code on app startup - 4 3
  • Generate docs - 4 4
  • One controller with many routes - 4 3
  • Custom sbt tasks - 4 4
  • bootstrap play console - 3 3
  • creating play plugins - 3 3
  • create custom modules - 4 2
  • using dependency injection with play controllers - 4 3

Web Services and Integration

Must haves

  • Web sockets - 5 5
  • Server Sent Event - 5 5
  • role-based auth - 5 5
  • Background processing - 5 5
  • Respond with different content types - 5 5
  • HTTP basic auth - 5 5
  • Call REST web services - 5 5
  • Parse JSON - 5 5
  • request body parsing using BodyParser - 5 5
  • SSL support - 5 5
  • Microservices in Play

We will probably have no time for these

Being Reactive

  • Large file uploads - 4 4
  • Working with multiple data streams - 5 5
  • Create custom Iteratee and Enumerator - 5 5
  • Future composition - 5 5
  • Using Akka actors from Play - 5 5
  • Using actors to communicate between play apps
  • Using multiple dispatchers - 5 5
  • Create isolated failure zones - 5 5
  • Facebook bigpipe
  • Rx ??

Data Access

  • Database evolutions - 5 4
  • debug sql calls - 4 5
  • redis - 5 4
  • Mongo - 4 5
  • Using Slick with Play - 5 5

User Interface

  • M17n - 4 4
  • scalate templates - 4 4
  • Sass - 3 3
  • Pagination (with Slick?) - 4 3
  • Custom error page - 4 3
  • Integrate with AngularJS? - 4 4

Play in Production

  • Distributing Play - 5 5
  • Deployment - 4 4
  • Logging - 4 3
  • Troubleshooting - 5
  • Performance tuning(we probably need to break it down)
  • Monitoring Play applications - 5 5
  • Serving static assets separately (cdn?) - 5 5
  • Using configuration file - 5 5
  • Version-ing assets - 3 4
  • Gziping response - 4 4

Testing

  • Integration testing - 5 5
  • Browser based testing - 3 4
  • Unit testing - 5 5
  • Testing templates - 5 5
  • Hooking in dependency injection framework - 3 4
  • Testing on source change (one pager) - 5
  • running test with test configuration - 5 5