Win a copy of Kotlin in Action this week in the Kotlin forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Mastering EJB - architecture recommendation  RSS feed

 
Blake Minghelli
Ranch Hand
Posts: 331
  • Mark post as helpful
  • send pies
  • 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?
     
    Karthik Guru
    Ranch Hand
    Posts: 1209
    • Mark post as helpful
    • send pies
    • 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.
     
    • Post Reply Bookmark Topic Watch Topic
    • New Topic
    Boost this thread!