Jeff Davidson wrote:
> We are designing a system based on J2EE and EJB which needs to service thousands
> of client applications. Originally we thought that each client would interact
> with one stateful session EJB in order to collect & cache data pulled from
> corporate databases. However, ass I've been reading more on EJBs, it sounds
> like this may not be a very good approach in terms of scaling and
> performance. If we use stateless session beans, where can we cache the
> data retrieved from the database? We need the data for subsequent
> calls to a rules-based engine to have it process and return information
> which we then return to the client app. Then, as we collect information
> from the client app, we need to combine this with the data from the
> db to be able to make more requests to the rules-based engine. So we need
> to cache it somewhere, but where?
Perhaps you should question your own assumptions about the performance penalties of
using Stateful Session beans, because the scenario you just described indicates that
a stateful session bean is what you need. Why reinvent a cache per client -- which
is what you need -- when stateful session beans provide that already.
-Richard
--
Author of Enterprise JavaBeans
Published by O'Reilly & Associates
EJB FAQ
http://www.jguru.com/faq/EJB
EJBNow.com
http://www.ejbnow.com
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
