EJB - love or hate?
EJB is liked by many and hated by some. Why? The main reasons I hear are: 1. memory and cpu hog 2. slow
Many times these can be contributed to bad implementation. For example fetching remote object by reference is a slow operation. If it is done in a loop, it will be slow. Re-factor the code and possibly move the code to the remote object or cache the references when fetched once.
Try not to use Sun's reference implementation, use JBoss (free), Weblogic etc. for faster performance. Try increasing the number of threads in Application Server for optimum performance.
Do you have bad EJB experience - like memory and resource hog, slow etc? Write to me at angsuman@taragana.com with subject [EJB problems].
EJB is liked by many and hated by some. Why? The main reasons I hear are: 1. memory and cpu hog 2. slow
Many times these can be contributed to bad implementation. For example fetching remote object by reference is a slow operation. If it is done in a loop, it will be slow. Re-factor the code and possibly move the code to the remote object or cache the references when fetched once.
Try not to use Sun's reference implementation, use JBoss (free), Weblogic etc. for faster performance. Try increasing the number of threads in Application Server for optimum performance.
Do you have bad EJB experience - like memory and resource hog, slow etc? Write to me at angsuman@taragana.com with subject [EJB problems].
posted by Angsuman Chakraborty | 11:01 PM
<< Home