ecscala VS Play

During my career break that I started in 2025, I started exploring the ever-changing Generative AI landscape. In Decemember, I was exploring Spring Boot as I hadn't used it in anger professionally having used other Java frameworks like Jersey, Play and I wanted to build something.

~/project$ sbt run [info] welcome to sbt 1.10.6 (Ubuntu Java 17.0.14) [info] loading settings for project scala-api-heroku-build from plugins.sbt... [info] loading project definition from /home/alvin/repositories/devspotlight/heroku/scala/scala-api-heroku/project [info] loading settings for project root from build.sbt... [info] loading settings for project docs from build.sbt... [info] __ __ [info] \ \ ____ / /____ _ __ __ [info] \ \ / __ \ / // __ `// / / / [info] / / / /_/ // // /_/ // /_/ / [info] /_/ / .___//_/ \__,_/ \__, / [info] /_/ /____/ [info] [info] Version 3.0.6 running Java 17.0.14 [info] [info] Play is run entirely by the community. Please consider contributing and/or donating: [info] https://www.playframework.com/sponsors [info] --- (Running the application, auto-reloading is enabled) --- INFO p.c.s.PekkoHttpServer - Listening for HTTP on /[0:0:0:0:0:0:0:0]:9000 (Server started, use Enter to stop and go back to the console...)

My major complain here is that, as far as being a web framework there is precious little information here about the framework. How does this framework scale with multiple requests? What concurrency strategy is it using (threads, processes, actors, etc?). Is this opinionated (it doesn't seem so but it also doesn't say it isn't either). How does this work with popular libraries x,y,z. The full docs have a little bit more information, but not a ton. But mostly there are some cute toy examples and "built in python" and thats about it.

Lets compare this with for example play https://www.playframework.com/ I know from this that it built on Akka, its stateless, aims for predictable resource consumption, has non-blocking io, etc. There is a ton of really important information on what does this web framework actually do that is really important when you are making a choice of a framework.

I have no idea how good this framework is, but besides a few toy examples, I can't see anything that makes me thing "wow this is great I need to use this".

A web application framework for Java/Scala: https://www.playframework.com/

Scala 3 migration isn't as simple as migrating other apps, you can track the work at https://github.com/playframework/playframework/issues/11260

And there are frameworks you can use to make development easier, like Play. And Java has plenty of choices for dependency injection frameworks.