Compare Play and spring.io 
- Users report that spring.io excels in application deployment with a score of 9.3, highlighting its seamless integration with cloud services, while Play's deployment capabilities are rated lower, indicating potential challenges in scaling applications effectively.
- Reviewers mention that spring.io offers superior development tools, scoring 9.0, which includes robust support for microservices architecture, whereas Play's development tools are perceived as less comprehensive, leading to a steeper learning curve for new developers.
- G2 users note that spring.io's testing features are highly rated at 9.3, with users appreciating its built-in testing framework that simplifies unit and integration testing, while Play's testing capabilities are rated lower, suggesting that users may face difficulties in ensuring code quality.
- Users on G2 highlight spring.io's database management capabilities, scoring 9.3, particularly praising its support for various databases and ease of integration, while Play's database management features are seen as less flexible, which could limit user options.
- Reviewers say that spring.io's ease of setup is rated at 8.9, with many users appreciating the extensive documentation and community support, whereas Play's setup process, rated at 8.3, is often described as more complex and less intuitive.
- Users report that spring.io's quality of support is rated at 8.4, with many citing responsive customer service and helpful resources, while Play's support, rated at 7.4, is viewed as lacking in timely assistance, which can be a drawback for users needing immediate help.
You can transcend skill sets by using Play! as an intermediary between having your development team learn a more modern JVM language (Scala) and Java. The framework's power can still very easily be seen using Java methods, and in-fact I personally prefer to...
Really too small There is more agreement Few Chinese resources
It really helps me focus on my business features instead of worrying about configuration, boilerplate code and thinks like those. It can be integrated with almost any technology I usually use: relational database, mongoDB, redis, JMS, etc... Moreover...
It seems that jHipster is WAAAAY more powerful with more combinations and frameworks than Spring Roo. Frontend is old way of doing web. Spring Roo is still using MVC pattern. While in jHipster you can use Angular, React,Vue. You can setup as...
You can transcend skill sets by using Play! as an intermediary between having your development team learn a more modern JVM language (Scala) and Java. The framework's power can still very easily be seen using Java methods, and in-fact I personally prefer to...
It really helps me focus on my business features instead of worrying about configuration, boilerplate code and thinks like those. It can be integrated with almost any technology I usually use: relational database, mongoDB, redis, JMS, etc... Moreover...
Really too small There is more agreement Few Chinese resources
It seems that jHipster is WAAAAY more powerful with more combinations and frameworks than Spring Roo. Frontend is old way of doing web. Spring Roo is still using MVC pattern. While in jHipster you can use Angular, React,Vue. You can setup as...
