Issues regarding using EJB - Entity / Stateless
My web application may have about 10000 logins at a time and at my design stage should i decide about using all throughtout only stateless session bean with methods to connect to databse being informix9.2, and invoke any kind of DML statements directly, rather than having a CMP/BMP Entity bean.
My end user may have the least of client hardware config and must still succeed in using my web application.
My application deals with blobs and images (basically MPEG files) the amount of load on the Internet Server as well and my end users CPU time must be considered now.
My concern :
If i decide on a CMP Entity bean - saves a lot of my efforts of transactions handling and rest. But i am worried about my Internet service mgr as well as my application server WebSphere as to whether the load of 10000 logins approx. multiplied by say 10 CMP Entity beans . what will be the scenario then ?. Server crash
Will it be efficient in perfomance and the best proposal to have a stateless session bean performing the DMLs in methods and the developer handling the transactions.
For such heavy transaction based and highly used concurrent users application is CMP/BMP Entity bean suggested to do the DML on database.. or can stateful session bean be of any good help with any work arounds.
or
Stick to safer design 'Stateless session beans'
