To be honest if I were starting again today I would not have used java except for performance limited jobs exposed as web services. Even those I would be tempted to write in Go. I may have used it for interfacing with some of the archaic XML APIs I have to interface with, JAXB does a good job with dealing with shenanigans in the format I've found.
That said to get to your question, I don't have experience with either at the same scale as the EE6 app. I have fiddled with both some to get a feel as I was deciding what the path away from the EE6 stuff I would take. I have ditched hibernate for Ebean (Ebean is the ORM that comes with Play). I've also started writing most of the controllers in Groovy, which comes from messing with grails. Both these changes have been awesome and significantly simplified the project.
Comments
To be honest if I were starting again today I would not have used java except for performance limited jobs exposed as web services. Even those I would be tempted to write in Go. I may have used it for interfacing with some of the archaic XML APIs I have to interface with, JAXB does a good job with dealing with shenanigans in the format I've found.
That said to get to your question, I don't have experience with either at the same scale as the EE6 app. I have fiddled with both some to get a feel as I was deciding what the path away from the EE6 stuff I would take. I have ditched hibernate for Ebean (Ebean is the ORM that comes with Play). I've also started writing most of the controllers in Groovy, which comes from messing with grails. Both these changes have been awesome and significantly simplified the project.