I've heard that the general rule of thumb is that if the data is for the
most part just listable -- you should use a stateless session bean
w/ JDBC. For example, if you have an E-Commerce site with 100,000
SKUs, I would think the stateless session bean approach would be
better. Definitely would perform better.
Is anyone out there running a production site with a large number of
entity beans? I'd be curious to know how it performs.
Deciding between stateless session beans w/ JDBC or entity beans has
definitely been the big issue in designing my application. I still don't
feel
confident in making a decision. I guess trying it both ways would be the
right way
to do it -- but who's got time for that? =)
Anyone have any experiences to share?
Neal
===========================================================================
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".
