title: Is Play Framework suitable for asynchronous background processing?
body: <p>I'm going to build a web application that's going to host urban games.</p>
  
  <p>A user visits my website, clicks "Start game" and starts receiving some SMS messages when gets to some location and has to answer them to get points.</p>
  
  <p>Is Play suitable for this kind of application? After clicking the "start game" button some logic has to go on its own course. How would I handle checking geolocation of the players (I have API for that) parallely? I would like to ping the player every ~5 sec. and do some logic. The user of course has to be able to use the web application at the same time as it's processing his location, assigning points, sending and receiving messages etc.</p>
  
  <p>So to sum up: I want an application written in Play that starts a separate thread for a game after clicking "start game" and other users are able to view their data (statisctics etc.), while the threads work their way with the game logic.</p>
  
  <p>I found something like <a href="http://www.playframework.com/documentation/1.2/jobs" rel="nofollow">jobs</a> but they are documented for version 1.2. After some reading it turned out that <a href="http://www.playframework.com/documentation/2.0.2/JavaAkka" rel="nofollow">Akka</a> is the recommended one now but it uses and actor model.</p>
  
  <p>Is Play + Akka a good choice for my project?</p>