The ACID6 model introduced a tightly coupled transaction processing method. That is, this
approach was designed to tackle local repository reliability issues and to offer short-lived 7 transaction
solutions, meaning successful transaction results are guaranteed only for a short period of
time. Conversely, a service-oriented interoperable computing landscape necessitates a model that
can handle service interaction and collaboration in complex and aggregated structures. In addition,
it requires transaction integrity among loosely coupled service formations dispersed across
multiple lines of business and organizations. A service-oriented transaction scheme must also be
commissioned to resolve long-lived8 transaction challenges. In a service-oriented environment, a
transaction can last hours or even days.
What is the way to ensure atomicity of transaction activities in such a service-oriented
loosely coupled model? Is it feasible to lock up resources for a long period of time until a
transaction is completed? Can a service-oriented transaction model use the synchronous communication
approach devised by the ACID model? Can transaction activities be halted until results
are returned?
283
284 Ch. 14 Service-Oriented Transaction Model
These questions represent the major challenges facing today??™s service-oriented transaction
processing environment. Many service-oriented architecture (SOA) practitioners are occupied with
carving out transaction strategies based on the atomistic short-lived ACID paradigm while at
the same time enabling long-lived transaction capabilities.
Pages:
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494