You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Rajith Attapattu <ra...@gmail.com> on 2006/01/05 16:02:21 UTC
[Axis2] Clustering - Lets get the ball rolling
Hi All,
I have seen some intrest in clustering but I see that there is no ongoing
discussion or any clear requirments on this topic.
What I would like to do is to start some discussion and gather some momentum
around this so we can flush out the requirments/expectations of clustering
for Axis2.
I can volunteer to cordinate the effort, but I really need people to come
out with suggestions and expectations.
To start with I would like to pose a few questions and get the ball
rolling...
1. What is the basic unit of clustering from Axis2 point of view ?
2. Since web services are more xml driven than object driven, can a object
focused clustering solution be used within Axis2 ?
3. What are some of the challengers or limitations we already know ?
4. If we consider a homogenous collection of web services deployed on
several nodes what will be the users expectations on clustering?
a.) Configuration data to be clustered to all nodes vs One time manul
update ???
b.) If a web service fails during a request how intelligent should axis2
be in determining wether to transparently move the session/request to
another node?
c.) What policies are we going to support ??? Sticky sessions vs
no-sticky sessions and several other variations of this.
We should provide an API for people to write there own policy/impl
for clustering stratergy.
d.) we support several transports, therefore how can we generalize our
clustering support to be applicable within all transports ??
Comments/suggestions are very welcomed !!!
Regards,
Rajith Attapattu.
Re: [Axis2] Clustering - Lets get the ball rolling
Posted by Rajith Attapattu <ra...@gmail.com>.
Saminda,
I think you have raised a very important point.
Steve echoed simiilar thoughts like let the container/framework/environment
where Axis2 is deployed or built on handle the clustering and fail-over
stratergies.
Steves point is that Axis2 is somewhat ready to cluster as it is.
So what are your thoughts on that?? Is Axis2 cluster ready depending on the
container or is there a real need to do more to make it more cluster aware?
Sanjiva also had some thoughts on clustering and would be helpful if u can
comment on this thread.
I guess the question is
a) are we going to make Axis2 to cluster on it's own
b) or are we going to let the container/framework/environment where Axis2 is
deployed or built on handle these concerns? If so is Axis2 ready-to-cluster
as it is?
Another important point what I like to raise is, do we have a clear
understanding of what aspects needs to be clustered in Axis2, which will
then give us a clear indication of wether Axis2 is
already "ready-to-cluster" or more work needs to be done.
If we can get that sorted out then maybe we can go talk to the AppServer
people or any other framework and ask/try-it-out to see if these
appservers/frameworks can handle/facilitate clustering with Axis2 as it is
or more things need to be done.
Regards,
Rajith Attapattu.
On 1/6/06, Saminda Abeyruwan <saminda@opensource.lk > wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Rajith Attapattu wrote:
> > Hi All,
> >
> > I have seen some intrest in clustering but I see that there is no
> ongoing
> > discussion or any clear requirments on this topic.
> >
> > What I would like to do is to start some discussion and gather some
> momentum
> > around this so we can flush out the requirments/expectations of
> clustering
> > for Axis2.
> >
> > I can volunteer to cordinate the effort, but I really need people to
> come
> > out with suggestions and expectations.
> >
> > To start with I would like to pose a few questions and get the ball
> > rolling...
> >
> > 1. What is the basic unit of clustering from Axis2 point of view ?
> >
> > 2. Since web services are more xml driven than object driven, can a
> object
> > focused clustering solution be used within Axis2 ?
> >
> > 3. What are some of the challengers or limitations we already know ?
> >
> > 4. If we consider a homogenous collection of web services deployed on
> > several nodes what will be the users expectations on clustering?
> > a.) Configuration data to be clustered to all nodes vs One time manul
> > update ???
> >
> > b.) If a web service fails during a request how intelligent should
> axis2
> > be in determining wether to transparently move the session/request to
> > another node?
> >
> > c.) What policies are we going to support ??? Sticky sessions vs
> > no-sticky sessions and several other variations of this.
> > We should provide an API for people to write there own
> policy/impl
> > for clustering stratergy.
> >
> > d.) we support several transports, therefore how can we generalize
> our
> > clustering support to be applicable within all transports ??
> >
> > Comments/suggestions are very welcomed !!!
> >
> > Regards,
> >
> > Rajith Attapattu.
> >
>
> Synapse is an ESB.It's one of the users of Axis2, still in incubation,
> which has a notion of Mediation. It's designed to provide support of
> clustering, routing, load balancing, fail over recovery, etc etc. in the
> web service world with Quality of Services such as WS-Security, WS-RM,
> WS-Addressing, etc, etc, thus, becoming a Mediation Framework for Web
> Services.
>
> Configuration of Synapse is based on Rules. Rules will say how to do
> clustering, routing. load balancing, fail over recovery etc. for the
> incoming message. It will switch on/off qos such as Sec, RM etc.
>
> Synapse can work as a proxy. Thus, can be a mediator between legacy
> systems or it can route messages among multiple transports.
>
> Thank you
>
> Saminda
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFDvhUCYmklbLuW6wYRAoaDAJ9lNf40pgEbZWVCBQ/W3JkeTt9IcACfZLrl
> wQWrBcDEvQm9OoW8kDGVRXQ=
> =VDH5
> -----END PGP SIGNATURE-----
>
Re: [Axis2] Clustering - Lets get the ball rolling
Posted by Saminda Abeyruwan <sa...@opensource.lk>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Rajith Attapattu wrote:
> Hi All,
>
> I have seen some intrest in clustering but I see that there is no ongoing
> discussion or any clear requirments on this topic.
>
> What I would like to do is to start some discussion and gather some momentum
> around this so we can flush out the requirments/expectations of clustering
> for Axis2.
>
> I can volunteer to cordinate the effort, but I really need people to come
> out with suggestions and expectations.
>
> To start with I would like to pose a few questions and get the ball
> rolling...
>
> 1. What is the basic unit of clustering from Axis2 point of view ?
>
> 2. Since web services are more xml driven than object driven, can a object
> focused clustering solution be used within Axis2 ?
>
> 3. What are some of the challengers or limitations we already know ?
>
> 4. If we consider a homogenous collection of web services deployed on
> several nodes what will be the users expectations on clustering?
> a.) Configuration data to be clustered to all nodes vs One time manul
> update ???
>
> b.) If a web service fails during a request how intelligent should axis2
> be in determining wether to transparently move the session/request to
> another node?
>
> c.) What policies are we going to support ??? Sticky sessions vs
> no-sticky sessions and several other variations of this.
> We should provide an API for people to write there own policy/impl
> for clustering stratergy.
>
> d.) we support several transports, therefore how can we generalize our
> clustering support to be applicable within all transports ??
>
> Comments/suggestions are very welcomed !!!
>
> Regards,
>
> Rajith Attapattu.
>
Synapse is an ESB.It's one of the users of Axis2, still in incubation,
which has a notion of Mediation. It's designed to provide support of
clustering, routing, load balancing, fail over recovery, etc etc. in the
web service world with Quality of Services such as WS-Security, WS-RM,
WS-Addressing, etc, etc, thus, becoming a Mediation Framework for Web
Services.
Configuration of Synapse is based on Rules. Rules will say how to do
clustering, routing. load balancing, fail over recovery etc. for the
incoming message. It will switch on/off qos such as Sec, RM etc.
Synapse can work as a proxy. Thus, can be a mediator between legacy
systems or it can route messages among multiple transports.
Thank you
Saminda
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDvhUCYmklbLuW6wYRAoaDAJ9lNf40pgEbZWVCBQ/W3JkeTt9IcACfZLrl
wQWrBcDEvQm9OoW8kDGVRXQ=
=VDH5
-----END PGP SIGNATURE-----
Re: [Axis2] Clustering - Lets get the ball rolling
Posted by Steve Loughran <st...@apache.org>.
Rajith Attapattu wrote:
> Hi All,
>
> I have seen some intrest in clustering but I see that there is no
> ongoing discussion or any clear requirments on this topic.
>
> What I would like to do is to start some discussion and gather some
> momentum around this so we can flush out the requirments/expectations of
> clustering for Axis2.
>
> I can volunteer to cordinate the effort, but I really need people to
> come out with suggestions and expectations.
>
> To start with I would like to pose a few questions and get the ball
> rolling...
>
> 1. What is the basic unit of clustering from Axis2 point of view ?
>
> 2. Since web services are more xml driven than object driven, can a
> object focused clustering solution be used within Axis2 ?
Publishing xml-docs to a tuple space of some form or other is the
alternative, but you can use java serialization to store xml graphs too.
>
> 3. What are some of the challengers or limitations we already know ?
>
> 4. If we consider a homogenous collection of web services deployed on
> several nodes what will be the users expectations on clustering?
> a.) Configuration data to be clustered to all nodes vs One time manul
> update ???
>
> b.) If a web service fails during a request how intelligent should
> axis2 be in determining wether to transparently move the session/request
> to another node?
It shouldnt try. Caller gets to ask again. Maybe some load balancer up
front can change this, but since there are so many interesting ways to
fail, and indeterminite state of a failure unless everything is
transaced, you dont want to go there.
>
> c.) What policies are we going to support ??? Sticky sessions vs
> no-sticky sessions and several other variations of this.
> We should provide an API for people to write there own
> policy/impl for clustering stratergy.
Seems to me that Axis2 ought to be ready-to-cluster, inside whatever the
app server provides (e.g jboss, geronimo, whatever I do with Anubis).
>
> d.) we support several transports, therefore how can we generalize
> our clustering support to be applicable within all transports ??
>
Talk to the app server people, would be my guess.