W3C home > Mailing lists > Public > www-ws@w3.org > November 2004

Re: Stateful Web Services...

From: Mark Baker <distobj@acm.org>
Date: Tue, 2 Nov 2004 16:49:24 -0500
To: David Orchard <dorchard@bea.com>
Cc: www-ws@w3.org
Message-ID: <20041102214924.GE12860@markbaker.ca>

On Mon, Nov 01, 2004 at 10:22:37PM -0800, David Orchard wrote:
> Needless to say, Roy's claim is not backed up by any references so my
> claim is just as valid on the face of it.

I wouldn't say that.  Roy backed up his claim by describing exactly how
scalability was negatively impacted; by giving the server more freedom
to manage its own resources how and when it sees fit.  If you know of
some means by which that problem can be eliminated (effectively or
actually) with stateful services, I'd really(!) like to hear it since
Roy's explanation jives with my experience.

>  Also, my company does ship
> software that deals with high reliability and scalability systems so we
> do know a thing or to.

Apparently! 8-)

"EJB Providers can increase application scalability by using stateless session beans wherever appropriate. With stateless
session beans, the WebLogic Enterprise EJB container can freely pool instances, allocate instances as needed, and apply lo
ad balancing strategies to distribute the load across different servers within the domain."
 -- http://e-docs.bea.com/wle/tuning/tsejb.htm

Of course, load balancing can occur even with stateful services, so long
as some part of the message uniquely references the shared contextual
state.  But the other advantages seem specific to stateless services.

Cheers,

Mark.
-- 
Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca
Received on Tuesday, 2 November 2004 21:47:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:46 GMT