The rule of thumb is: defer state from your custom developed services whenever possible, especially when creating agnostic (generically reusable) services. This means that you can have intentionally stateful "system" services that take care of state management in order to alleviate others from having to do so. Also, when your middleware implements WS-* extensions, like context management (WS-Coordination), you will notice that it automatically provides stateful Web services that fulfill this role. Other options for statement management also exist, like the use of middle tier databases or an orchestration engine that will centralize state information along with business process logic.
Dig Deeper on Service-oriented architecture (SOA)
Related Q&A from Thomas Erl
In this expert answer, 'Cloud Computing' author and consultant Thomas Erl discusses current and emerging cloud standards. Continue Reading
Cloud expert Thomas Erl discusses how community clouds work and which types of organizations might most benefit from using them. Continue Reading
Thomas Erl discusses the definition of what service statelessness means in relation to Web services and service-oriented architecture. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.