Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Play 2 vs Spring-boot, the Slant community recommends Spring-boot for most people. In the question“What are the best Java web frameworks?” Spring-boot is ranked 2nd while Play 2 is ranked 4th. The most important reason people chose Spring-boot is:
Boot is just a thin configuration layer over Spring Framework, as such it inherits all the strengths of Spring.
Specs
Question Ranking
Pros
Pro Very fast and easy to install, it is a revolutionary framework
Pro Great resources
With some basic starting tutorials and a fleshed out documentation, there will be no need to go asking others for help, there should be enough for a developer to find a solution.
Pro Asynchronous requests
Everything with Play has been built with asynchronous requests in mind. This will result in the application not blocking results while waiting on other operations. With this implemented your application can be developed with multiple threads in mind without worrying about hanging on one request before it completes another.
Pro Rapid application development
All error checking and testing done in the browser only needs a page refresh to show the latest updates. This is huge, allowing the ability to code in real-time and make quick edits. Without it the develop would need to reboot/recompile the entire application to test with new data.
Pro Supports Scala
Pro Inherits all of Spring's strengths
Boot is just a thin configuration layer over Spring Framework, as such it inherits all the strengths of Spring.
Pro Preconfigured starters
Pro Fast prototyping
Spring boot is built for fast prototyping.
Pro Kick down to Spring
Cons
Con Not backword-compatible
Applications that have been written in Play 1 will not be supported in Play 2 as the core of the framework was rewritten in Scala. This includes plugins that were working in Play 1 as well.
Con Becoming a Scala framework
As Play continues to develop and mature it seems as if it is becoming less of a Java framework as the core has been rebuilt in Scala. This may deter adopters.
Con Steep learning curve
Con Lacking in UI development
While actually very good and with a very complete and rich feature set to develop and maintain code on the server side, it still doesn't provide any rich framework for building good user interfaces.
