EJB3 was way later than Spring/hibernate. Websphere/Weblogic never recover since that time. Today, Spring/Hibernate is actually more powerful than an EJB3 solution, though the latter is arguably simpler. The issue is that Websphere/Weblogic charges hefty fee, and it doesn't perform as well as Tomcat. Other than rare case like two-phase commit, I don 't see the benefits of ejb servers at all. Jetty is also being used a lot as an embedded server. This can be handy when you are running a non-web server so you don't need a web container at all, nevertheless you want to expose some information, health check etc., or even a web service interface. Jetty is a great choice in such scenario but it's usage is light, not as battle-proof as Tomcat.
【在 g*****g 的大作中提到】 : EJB3 was way later than Spring/hibernate. Websphere/Weblogic never recover : since that time. Today, Spring/Hibernate is actually more powerful than an : EJB3 solution, though the latter is arguably simpler. : The issue is that Websphere/Weblogic charges hefty fee, and it doesn't : perform as well as Tomcat. Other than rare case like two-phase commit, I don : 't see the benefits of ejb servers at all. : Jetty is also being used a lot as an embedded server. This can be handy when : you are running a non-web server so you don't need a web container at all, : nevertheless you want to expose some information, health check etc., or even : a web service interface. Jetty is a great choice in such scenario but it's