I&#x27;ve also been working with Play Framework and I&#x27;m pretty impressed at how awesome and easy to use everything is. The documentation is great, the performance is great.<p>I&#x27;m using it for just a web API, and I&#x27;ve had several scala developers tell me to use akka-http instead because it is simpler. I tried, but the route api is quite horrid in comparison to a simple file-based routing description, and the utilities (like the web service client) were a nightmare to work with and debug. And to top it off, the performance was still worse than play. Maybe all of that will get better, but as of right now, Play is hard to beat.<p>My only complaints so far:<p>1) Slick is bloated and kludgy and still produces bad SQL queries...I&#x27;ve resorted to using the plain SQL interface which is nice, but not great.<p>2) It could use some support for API description languages like swagger.<p>3) Testing your code using the dependency injection framework has been very unintuitive (I&#x27;m pretty new to dependency injection frameworks though, so maybe it&#x27;s just me).<p>4) Action composition has been a lot harder than expected (for example: <a href="http:&#x2F;&#x2F;stackoverflow.com&#x2F;questions&#x2F;36683676&#x2F;play-action-composition-hardcoding-parameterized-parser" rel="nofollow">http:&#x2F;&#x2F;stackoverflow.com&#x2F;questions&#x2F;36683676&#x2F;play-action-comp...</a>)<p>5) I wish I didn&#x27;t have to deal with an opaque SBT plugin, and that the project just used a regular SBT project structure. I realize there are reasons for needing a plugin (like codegen for routes, etc.), but at least document how to work with the plugin better. SBT is like working with a black box as it is, no need to make it worse.