Fast Lane reader pattern

[Andron Dre]

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).]

[Matts Smith]

Originally posted by Andron Dre:
Hi
But they never said about scalability and pooling.
So by accessing it without ejb, we are loosing all scalability.

Hi there,
First pooling is provided by the appserver, not only to EJBs but to all other layers. About scalability, I think the first step to have a good scalability is to have "efficient" code. the reason why fast-lane is better (even if in theory EJBs scale better because they can be easily distributed) is that the code is WAY faster without EJBs. Also you can easily distribute servlet engines, which would bring scalability.
hope it answers your question