> Assuming that my site receives
> 100000 hits per second or say atleast 100 hits per second then each time
my
> session bean will have to hit the DB. And hitting the DB and returning the
> resultset involves time and also chews up resources. Isn't it?
First, figure out if it's 100000 or 100. That's one heck of a difference.
DB caching itself will be much trickier if you have 100000 different users
every second querying their membership info. I'd love to know your business
with so many concurrent users!
You could use your stateless session bean to be the the service provider and
an entity bean to represent the membership object. The session bean will
encapsulate the biz logic while the entity will encapsulate the membership
info.
David
===========================================================================
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".
