Comments on: Scalability Article up on InfoQ http://www.udidahan.com/2008/04/10/scalability-article-up-on-infoq/ Enterprise Development Expert & SOA Specialist Sat, 11 Feb 2012 15:16:10 -0600 http://wordpress.org/?v=2.8.4 hourly 1 By: udidahan http://www.udidahan.com/2008/04/10/scalability-article-up-on-infoq/comment-page-1/#comment-37503 udidahan Sat, 06 Nov 2010 12:15:38 +0000 http://udidahan.weblogs.us/2008/04/10/scalability-article-up-on-infoq/#comment-37503 Maninder, I'd recommend not worrying too much about the definition, but rather which type of architecture is *useful*. That being said, the original definition was number 1. Maninder,

I’d recommend not worrying too much about the definition, but rather which type of architecture is *useful*. That being said, the original definition was number 1.

]]> By: Maninder http://www.udidahan.com/2008/04/10/scalability-article-up-on-infoq/comment-page-1/#comment-37496 Maninder Thu, 04 Nov 2010 18:04:54 +0000 http://udidahan.weblogs.us/2008/04/10/scalability-article-up-on-infoq/#comment-37496 Udi, Do you know of an authoritative source that defines the semantics around stateful and stateless services? I come across different meanings of stateless service Definition 1) Ability for any server in your application farm to handle a request. This simply means that request handling does NOT require server affinity. Hence, any server can handle the request. Though this does not mean that there is no saga associated with the request handling. It simply means that saga is globally avilable, either via distributed cache or database and any server can pull the saga and proceed to process the message. 2.Definition 2 :- Share nothing architecture Each request is self contained and there is no shared saga. Hence any server can process the request with just the data available within the request. Though in this case, you could argue that saga could be serialized with response to the client and hence, each request comes with data + saga and server can interpret saga and process data. Can you please help point to the right direction that can define stateless service so that i can look at above 2 scenario and say if they are both stateless or stateful? Thank you. Udi,
Do you know of an authoritative source that defines the semantics around stateful and stateless services?
I come across different meanings of stateless service
Definition 1) Ability for any server in your application farm to handle a request.
This simply means that request handling does NOT require server affinity. Hence, any server can handle the request. Though this does not mean that there is no saga associated with the request handling. It simply means that saga is globally avilable, either via distributed cache or database and any server can pull the saga and proceed to process the message.

2.Definition 2 :- Share nothing architecture
Each request is self contained and there is no shared saga. Hence any server can process the request with just the data available within the request. Though in this case, you could argue that saga could be serialized with response to the client and hence, each request comes with data + saga and server can interpret saga and process data.

Can you please help point to the right direction that can define stateless service so that i can look at above 2 scenario and say if they are both stateless or stateful?

Thank you.

]]> By: Durable Messaging Dilemmas http://www.udidahan.com/2008/04/10/scalability-article-up-on-infoq/comment-page-1/#comment-27573 Durable Messaging Dilemmas Thu, 17 Jul 2008 22:41:39 +0000 http://udidahan.weblogs.us/2008/04/10/scalability-article-up-on-infoq/#comment-27573 [...] idempotent messages that could be resent as many times as necessary. You can read more about it here. This solution isn’t viable for other kinds of interactions but was just what we needed to [...] [...] idempotent messages that could be resent as many times as necessary. You can read more about it here. This solution isn’t viable for other kinds of interactions but was just what we needed to [...]

]]>