Is EJB still popular Web Architecture?
One could argue yes or no … Yes because EJB has evolved enough with EJB 3.0 to keep pace with the demands of modern Web application developers. Historically, EJB has suffered from ease-of-use issues, which have largely been addressed by the 3.0 spec. Moreover, JPA (the persistence solution in EJB 3.0) is very powerful and matches what Hibernate can do using simple annotations in your beans. On the other hand, you could argue against EJB because POJO containers such as Spring offer many of the same capabilities as EJBs without requiring a full application server. So I think it comes down to the software team’s personal taste and IT infrastructure. If the environment is already using a mature EJB 3.0 application server, then EJB 3.0 might be the right way to go. On the other hand, if you just have Tomcat or similar, then you can get most (if not all) the capabilities of EJB using a POJO container like Spring.