December 2008
Beginner
320 pages
8h 52m
English
Content preview from Requirements Modelling and Specification for Service Oriented Architecture
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
2.5. Stateless Services
As we saw in Chapter 1, services are usually regarded as 'stateless'. An object, service, system or protocol is said to be stateless if it does not keep a persistent state between transactions. Services that do have this property are called stative[]. It is a axiom of the architectural vision or rationale of SOA that all services should be stateless.
[] I refuse to use the utterly barbarous 'stateful' since there is already a perfectly good word in existence and which anyway means something quite different - according to the OED: full of state or dignity, stately.
A stateless service treats each message as an independent transaction that is unrelated to any previous request. For example, a web server is stateless because processes requests to display pages require neither any context nor any memory of previous requests. Contrast this with an FTP server conducting an interactive session with a user; a request to the server for a file might assume that this user has been authenticated and that the current directory and file transfer mode have been set, requiring a remembrance of things past.
Statelessness helps ensure loose coupling and reusability. Statelessness also simplifies service design; services do not need to allocate memory dynamically to deal with conversations in progress or worry about freeing it if a client crashes mid-transaction.
The main disadvantage of statelessness is that it may be necessary to include more information in messages. This ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.