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.
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.
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi