Except Spring also has its own way of doing beans, people keep forgeting about it.
“Bean” is a broad term. It certainly didn't have a container to run standalone modules as ejb-jars. Spring is just a framework, not an application server with isolated classloaders that the JaveEE application servers were based on.
I stand by my comment, rather Websphere than Kubernets/YAML/WASM.
Agree
Agree
Comments
Except Spring also has its own way of doing beans, people keep forgeting about it.
By the way, Orleans powers Halo servers.
I stand by my comment, rather Websphere than Kubernets/YAML/WASM.
“Bean” is a broad term. It certainly didn't have a container to run standalone modules as ejb-jars. Spring is just a framework, not an application server with isolated classloaders that the JaveEE application servers were based on.
But Spring Boot with its embedded HTTP server and internal infrastructure is certainly more than just a framework. It has its own class loade (launchedurlclassloader). See https://dzone.com/articles/spring-boot-classloader-and-class...
Piranha Cloud on the other hand runs Jakarta EE code without any class loader of its own. See https://blogs.oracle.com/javamagazine/post/you-dont-always-n...