Using Session Bean as session facade 2005-03-31 - By Shanmugavelu, Subramaniam (Cognizant)
Back
Won't the scalability take a big hit if a singleton is used by all
client? I remember working in a project where this problem happened. A
POJO that was designed as a Singleton became the bottleneck to
performance.
--
Subra
Subramaniam Shanmugavelu
subramaniam.shanmugavelu@(protected)
V-net: 48301
Phone: +91 44 52098301
-- --Original Message-- --
From: An interest list for Sun Java Center J2EE Pattern Catalog
[mailto:J2EEPATTERNS-INTEREST@(protected)] On Behalf Of Mich
Hagdishovich
Sent: Friday, April 01, 2005 1:05 AM
To: J2EEPATTERNS-INTEREST@(protected)
Subject: Re: Using Session Bean as session facade
Using session beans improves scalability, essentially the same way you
can implement your own caching scheme to improve scalability.
Rather than creating objects all the time (one to handle each client)
and then releasing them for garbage collection, you can use session
beans, in which case the EJB container does the task of creating the
pool of objects to use and puts lesser burden on object creation and
garbage collection. It is the same principle, only difference being,
rather than coding this pooling mechanism yourself, you let the jboss or
bea developers do this. There is more to session beans, but the pooling
is a major contributor to scalability. [Also, if you are using
transactions, it is easier to simply use session beans so container
starts and end transactions, but we wont go into that since you are
happy with the way it is working for you already.]
If however, your system does not require any state at all (no state
between two HTTP requests by a user), then you dont need session beans
at all, and you dont need to implement any pooling. You can simply use
singleton business classes, and multiple clients can access the same
object without any problems. [This is assuming you can hold all
business classes in memory without hitting RAM limit.]
Mich Hagdishovich
Genetics Software www.kromosoft.com
On Wed, 30 Mar 2005 22:39 , Ranjeeth kumar <ranju1973@(protected)>
sent:
>All-
>Thanks for ur reply. What I should conlude is that using session
>Beans (in an non-entity bean scenario) will help scalability. is that
>right?
>
>still not convinced :)
>
>-vidyod
>
===================================================================Companion
Site: http://www.corej2eepatterns.com J2EE BluePrints:
http://java.sun.com/blueprints/corej2eepatterns
List Archive:
http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to
listserv@(protected)
This e-mail and any files transmitted with it are for the sole use of the
intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply e
-mail and destroy all copies of the original message.
Any unauthorized review, use, disclosure, dissemination, forwarding, printing
or copying of this email or any action taken in reliance on this e-mail is
strictly
prohibited and may be unlawful.
Visit us at http://www.cognizant.com
===================================================================Companion
Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
|
|
