Play VS Spring

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.

However do note, Play should be perfectly usable as well, and it's still maintained by the community: https://github.com/playframework/playframework/issues/11649

In university I learned a bit of Java, so maybe I could use it professionally I guess?. There were many options to choose from. DropWizard, Spark, Play Framework. But the more documented one in the internet I found was Springboot, besides there were some courses in spanish and some friends that knew something about Springboot, so I give it a chance.

For a backend web server I use Play - https://www.playframework.com/ which I find to be the easiest one as a backend web server. For learning/using spark I found this course from coursera to be very useful. https://www.coursera.org/learn/scala-spark-big-data

This interface is a simplified version of real caching abstractions from Java technologies such as the ones from Spring or JCache (JSR-107). Both are part of quite complex solutions, having more generic types and different capabilities. Also, annotations would be preferred to using Cache directly in most Java applications.

Cross-post: Controller code using Unconfined Dispatcher #32032

Mitre really lost a lot of respect with CVE-2016-1000027. Every few weeks a warning that any SpringBoot 2.x project has a CVSS 9.8, which causes all sorts of heartache for those of us bound to CVE remediation. Every blasted security tool reports this one. Spring reviewed and rejected, as did our very, very large organization. Comically, this has become the CVE we use to see how our tools allow us to white/black list entries.

Thank god Spring dropped this interface in the Framework 6.x / Boot 3.x release, and the end for non-commercial support is this year for the old stuff.

https://github.com/spring-projects/spring-framework/issues/2...

Referring to https://github.com/spring-projects/spring-framework/blob/main/spring-web/src/main/java/org/springframework/web/bind/annotation/GetMapping.java, the value could have got assigned to any of the other members like name, path, params, etc. Is there any logic involved that enables the single value passed to the GetMapping annotation to be assigned to the value member?

This one. In short, JMS listeners stopped working randomly (of course only on Saturdays, and only under load), but at first we didn't know that and suspected the message broker at fault. We had quite extensive logging, but no observability on the broker. Can't remember all the details, but eventually we figured out it was the listener container, and I could reproduce it after debugging deeply into Spring code during a load test.

GitHub Stars: 51 K GitHub Link: https://github.com/spring-projects/spring-framework

It still has, but it is more of "imaginary" one (https://github.com/spring-projects/spring-framework/issues/24434).

Simple: Spring WebFlux does not require Servlet, but can adapt to it. We essentially built our own reactive HTTP abstraction, without any Servlet dependencies. Then we made adapters that use said abstraction for (Reactor) Netty and Servlet. Note that we have specific adapters for Tomcat, Jetty, and Undertow, relying on non-blocking native APIs.