title: Pros and Cons of JAX-RS, Playframework scala (REST backend), Web Api
body: <p>First am not sure if this question fits here well. However couldn't think of a better place to get help. I've been tasked to list the Pros and Cons of each of these {JAX-RS, Playframework scala, MS Web Api}. I've done some research but couldn't conclude as I've not used all three to great extent. Have used playframework to create simple REST app. Have read the Web Api tutorials but have not implemented anything. Did research on JAX-RS but haven't implemented anything either. Also most of our developers are familiar with C# and introductory Java. I am more inclined towards playframework due to Scala,Akka,no server restart and scalability etc but not clear about the cons. One thing am sure is JAX-RS is standard Java EE and Web Api is standard MS stuff. Below are some of the app requirements:</p>
  
  <ul>
  <li>Purely REST backend.       </li>
  <li>Proper authentication and authorization.</li>
  <li>Online secure payment {Paypal etc}    </li>
  <li>Single front-end for both mobile and desktop
  {angular/backbone/knockout..}</li>
  <li>Allow users to subscribe as companies or part of companies.</li>
  <li>Be able to connect to different databases without App restart.</li>
  <li>Code maintenance and readability. Other members should be able to pickup without hassle.</li>
  <li>Scalability</li>
  </ul>