Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
JavaRanch.com/granny.jsp
    Bookmark Topic Watch Topic
  • New Topic

Differentiate the ("use of EJB" vs "do not use EJB")?????

 
Christina Sanyos
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Report post to moderator
Differentiate the ("use of EJB" vs "do not use EJB")???
I know using EJB uses considerable system(web server)resources. Whats
the exact! demarkating line that we can differentiate the "use of
EJB" vs "do not use EJB".
The scale of the application determines the above question.
I came up with the following criteria that are factors to determine
the scale of the application:
(1). Number of records in the database(millions), if so how many
millions of records should be in the database???
(2). Number of clients accessing the application. How many clients
accessing the application would make you make your choice???
You can still develop an application that is robust with just a
normal, JSP, Servlet model. But it may not be that scalable.
Please post your opinion.

Thanks
Christina
 
Stan James
(instanceof Sidekick)
Ranch Hand
Posts: 8791
  • Mark post as helpful
  • send pies
  • Report post to moderator
Try listing your requirements and see which of the EJB features match up.
* Distributed objects
* Security model
* Scalability model (pooled object instances, etc)
* Session beans stateful or stateless
* Transaction management
* Entity beans BMP or CMP
* Standardized XML configuration
* etc. etc. etc.
If the answer is "none" say for a small, internal web site, don't bother. If you get good value from several of those, maybe EJB is just the ticket.
 
Ajith Kallambella
Sheriff
Posts: 5782
  • Mark post as helpful
  • send pies
  • Report post to moderator
Please continue the discussion under this thread. Current duplicate thread is being closed ..
 
    Bookmark Topic Watch Topic
  • New Topic