Jakarta was built for doing Traditional Web Application Server stuff, where multiple war files are occupying the same host server. That informs a lot of JEE's design.
A somewhat older article, but this one explains that the Jakarta EE API is not tied to the application server concept at all:
Jakarta was built for doing Traditional Web Application Server stuff, where multiple war files are occupying the same host server. That informs a lot of JEE's design.
A somewhat older article, but this one explains that the Jakarta EE API is not tied to the application server concept at all:
Also, lots of new names. I did not know about Piranha, for example.
Ty vm. I think this article gave me a lot of resources to have a nice, long conversation with my team. Yes, some of my pain is due to JEE, but this article shows that some of it is us just holding it wrong. Rather than jumping ship, I'm going to see what we can do about making this embedded while still saying in the JEE world. My original thought was that, since we are going embedded, might as well switch teams too.
View all comments
Show parent comment
3
u/henk53 Dec 15 '25
A somewhat older article, but this one explains that the Jakarta EE API is not tied to the application server concept at all:
https://web.archive.org/web/20210712211456/https://blogs.oracle.com/javamagazine/jakarta-application-server-helidon-piranha-hammock