The Trivadis Integration Architecture Blueprint: Implementation scenarios

Having understood the structure of the blueprint covered in the previous article on The Trivadis Integration Architecture Blueprint, this article will use individual scenarios to illustrate how the business pattern can be implemented using the Integration Architecture Blueprint.

This article by Guido Schmutz, co-author of Service-Oriented Architecture: An Integration Blueprint, will:

• Explain service-oriented integration scenarios
• Explain how an existing integration solution can be modernized using SOA, and describe a scenario that has already been implemented in practice

SOA: Implementing Service-Oriented Orchestrations

This article by Yuli Vasiliev, author of the book SOA and WS-BPEL, dicusses how to implement service-oriented orchestrations using WS-BPEL.

SOA: Implementing Message-Level Security

This article by Yuli Vasiliev, author of the book SOA and WS-BPEL, provides an example of how message-level security can be implemented in a Web services application.

Measuring SOA Complexity

This article by Michael Havey, author of SOA Cookbook, presents a formula for scoring SOA processes on complexity. We position complexity analysis as an important step in design oversight and governance. The approach we consider allows the governance team to rate each process as red, yellow, or green and to flag reds for rework. Intuitively, the 'complexity' of a process is the amount of branching or nesting in its graph. Flat form, scores well on complexity because it avoids excessive branching. Naïve processes score poorly. Our scoring method is a variant of McCabe cyclomatic complexity.