Abstract
The basic Web services infrastructure presented in the previous chapter suffices to implement simple interactions. In particular, it supports interactions where the client invokes a single operation on a Web service. When the interaction involves coordinated sequences of operations, additional abstractions and tools are needed to ensure the correctness and consistency of the interactions. This is no different from how conventional middleware evolved. RPCs support simple, one-call-at-a-time interactions between clients and servers. Adding guarantees to the interactions (e.g., transactions), requires additional protocols (e.g. two-phase commit) and an infrastructure that supports the necessary abstractions and the corresponding protocols (e.g., a TP monitor). The same applies to Web services. Once we go beyond simple, independent service invocations, new protocols, abstractions, and infrastructures are needed.
Keywords
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2004 Springer-Verlag Berlin Heidelberg
About this chapter
Cite this chapter
Alonso, G., Casati, F., Kuno, H., Machiraju, V. (2004). Service coordination protocols. In: Web Services. Data-Centric Systems and Applications. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-662-10876-5_7
Download citation
DOI: https://doi.org/10.1007/978-3-662-10876-5_7
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-07888-0
Online ISBN: 978-3-662-10876-5
eBook Packages: Springer Book Archive