Blogs: Spring or EJB ? What's the job market vote ?

  1. Spring or EJB ? What's the job market vote ? (1 messages)

    Editor's NOTE: The following blog post is taken from Spring's own blogger network which of course has a vested interest in promoting Spring, nevertheless, the cited data sources are from an independent job site. Rod Johnson blogs about the employment prospects and historical tendencies of employers requiring Spring and EJB knowledge, presenting a series of graphical illustrations around this particular job market and finishing up with a few points on EJB's decadence
    What does the decline of EJB mean to the industry as a whole, and for individual developers? * The fact that there are plenty of good technical reasons for the decline of EJB is heartening. It's one of many signs that it's harder today to impose solutions that have never been proven in practice than it was when J2EE emerged. This is a Good Thing. * It's not necessarily a rejection of standards–just a healthy rejection of standards that don't deliver results. As I've long argued, Java EE is more than EJB, and anyone who cares about the platform as a whole should be honest about the relevance and quality of the parts. * With better technology, business objects become POJOs, dependence on specific component models diminishes and labels become less important. * Moving away from EJB provides greater architectural flexibility, at a time when requirements are changing, through the rise of SOA and other forces, and companies are increasingly choosing lighter-weight deployment platforms. Although support for various parts of the EJB 3.0 model is available outside a full-blown application server (including in Spring 2.5, which offers the EJB 3.0 DI model in addition to its own, and in Pitchfork, which is used as the basis of WebLogic 10's EJB 3.0 implementation), EJB is a component model fundamentally predicated on deployment to a traditional application server. Frankly, the EJB era was an aberration. EJB failed to solve the problems of earlier this decade; it's still more inadequate to those of the future. Most of EJB's initial premises are now discredited; the specification's insistence on backward compatibility does not justify the tradeoffs it imposes. Its decline is a natural consequence of moving into a new, more fluid, world, where technologies such as OSGi and the humble Servlet API are proving much more relevant. Of course, as the absolute numbers are still very high, EJB is not going to go away completely any time soon. But the trend lines clearly suggest that it is becoming legacy.
    Read Rod's complete post : http://blog.springsource.com/main/2008/01/23/spring-overtakes-ejb-as-a-skills-requirement/
  2. Discussion on this topic by TSS community was undertaken in the following news post: http://www.theserverside.com/news/thread.tss?thread_id=48198#245982