A transaction should enable isolation
by locking short-lived activities while complying with lenient locking policies toward
long-lived activities.
??? Tightly coupled and loosely coupled transaction capabilities. A transaction should
enable execution of activities in tightly coupled and loosely coupled service-oriented
environments.
??? Orchestration but also choreography. A transaction should include both orchestrated
and choreographed activities.
LOGICAL DESIGN VIEW: SERVICE-ORIENTED TRANSACTION DIAGRAM
The service-oriented transaction diagram provides another perspective of an overall logical design
solution. This view conveys the interaction between services and their capacity to collaborate with
each other. Therefore, the transaction diagram is all about managing the business and technological
Logical Design View: Service-Oriented Transaction Diagram 285
processes, identifying service functionality, depicting message interchange between consumers
and their corresponding services, and devising orchestration and choreography of activities. The
requirement is to depict the sequence by which services communicate with their peers and associated
consumers and to elaborate on the synchronization aspect of transactions.
The transaction paradigm is the dominant aspect of the service-oriented transaction model.
Although the granular activities allow services and consumers to exchange information, transactions
are coarse functionalities that provide direction.
Pages:
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497