• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Mastering EJB - architecture recommendation

 
Ranch Hand
Posts: 331
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I recently finished reading Ed Roman's "Mastering EJB" and I have a question about one of his recommendations...
In the case where you have the option of using 2 application servers (A and B), you have the following options:
Option 1
  • Server A - Dedicated to web tier
  • Server B - Dedicated to business (EJB) tier

  • Option 2
  • Server A - Contains both web and business (EJB) tiers
  • Server B - Contains both web and business (EJB) tiers

  • For various reasons, he recommends using the Option 2.
    Also, if you have only one application server, then you are of course using the Option 2 with just server A.

    My questions:
    Doesn't that recommendation take the "distributed" part of EJB out of the picture?
    If so, then in light of newer technologies like Spring and Hibernate, is EJB still a good choice if you use his recommendation?
    Or, should we still use EJB because we have the flexibility of switching between Option 1 and Option 2?
     
    Ranch Hand
    Posts: 1209
    • Mark post as helpful
    • send pies
      Number of slices to send:
      Optional 'thank-you' note:
    • Quote
    • Report post to moderator

    Doesn't that recommendation take the "distributed" part of EJB out of the picture?


    But is'nt defining Local interfaces for EJBs , itself an acknowledgement of the fact that remoteness was a mistake? Esp entity beans, where features like CMR can be put to use only if you expose local interfaces for your entity beans. I'm not a technology expert so dont take my views seriously.
     
    reply
      Bookmark Topic Watch Topic
    • New Topic