Data on the Outside Versus Data on the Inside


Recently, a lot of interest has been shown in SOA (Service Oriented Architectures). In these systems, there are multiple services each with its own code and data, and ability to operate independently of its partners. In particular, atomic transactions with two-phase commit do not occur across multiple services because this necessitates holding locks while another service decides the outcome of the transaction. This paper proposes there are a number of seminal differences between data inside a service and data sent into the space outside of the service boundary. We then consider objects, SQL, and XML as different representations of data. Each of these models has strengths and weaknesses when applied to the inside and outside of the service boundary. The paper concludes that the strength of each of these models in one area is derived from essential characteristics underlying its weakness in the other area.

Extracted Key Phrases

Cite this paper

@inproceedings{Helland2005DataOT, title={Data on the Outside Versus Data on the Inside}, author={Pat Helland}, booktitle={CIDR}, year={2005} }