Hi by reading BluePrints patterns catalog, found Fast Lane reader pattern. All benefits that they describe are clear. But they never said about scalability and pooling. The example with catalog is a good one. In sites like Pet Store, functionality of displaying catalog is probably the most busiest one. So by accessing it without ejb, we are loosing all scalability. correct me if I am wrong
[This message has been edited by Andron Dre (edited December 13, 2001).]
posted 15 years ago
If you still want scalability of EJB with quick search, why don't you use DAO pattern. I think it's between Entity Bean finder methods overhead and fast-lane reader weak points. Rgrds
What are you doing? You are supposed to be reading this tiny ad!
the new thread boost feature brings a LOT of attention to your favorite threads