Integration Patterns

1
Integration Patterns
Ulrich Roxburgh

• Principal Consultant
• Microsoft Consulting Services

Director Services2 Ltd.
2
Patterns

• Mind sized chunk of information (Ward
  Cunningham)
• Shows a good solution to a common problem within
  a specific context

Context
Problem
Solution
3
Patterns

• Each pattern describes a problem which
• occurs over and over again in our
• environment, and then describes the core of
• the solution to that problem, in such a way
• that you can use this solution a million
• times over, without ever doing it the same
• way twice. 1
• 1 Christopher Alexander - A Pattern Language

4
Elements of Patterns

• Pattern name - Gives us a way to refer to the
  pattern.
• The problem - A particular pattern is applicable
  to certain types of problems. Part and parcel of
  a pattern is a description of what types of
  problems for which it is useful.
• The solution - Patterns define a particular
  conceptual solution to the problem.
• Consequences - Implementation decisions have
  certain tradeoffs. The consequences of these
  decisions and the forces underlying the pattern
  are essential aspects of the pattern.
• Design Patterns Elements of Reusable
  Object-Oriented Software,
• Gamma, Helm, Johnson, Vlissides.

5
Patterns

• Document simple mechanisms that work
• Provide a common vocabulary and taxonomy
• Enable solutions to be described concisely as
  combinations of patterns
• Enable reuse of architecture, design, and
  implementation decisions
• Provide distilled design knowledge
• Patterns are not source code files
• Patterns are not distributable components
• Patterns are not data structures

6
Convergence Pattern

• In the Convergence pattern, competitors from
  previously distinct industries start competing to
  satisfy the requirements of a specific customer
  set. There are three distinct flavors of this
  pattern product, in which product boundaries
  blur supplier, in which suppliers become one
  stop shops and complementor, in which companies
  combine to deliver greater value
• - Profit Patterns, Adrian J. Slywotsky

7
Global Bank Scenario
8
Key Use Cases

• View Scheduled Payments
• Schedule Payments
• Execute Scheduled Payment
• Receive Payment Response
• Add Payee

9
Portal Integration

• How can users efficiently perform tasks that
  require access to information that resides in
  multiple disparate systems?

10
System Connections
11
Integration Topologies
12
Pattern Model
13
View Scheduled Payments
14
Service Composition
15
Process Integration

• How do you coordinate the execution of a
  long-running business function that spans
  multiple disparate applications?

16
Pattern Model
17
Pattern Model
18
Execute Scheduled Payments
19
Network Model
20
Pattern Model
21
Implementation Model
22
Evaluations and Contact

• Dont forget to fill in your evaluations
• Presentation downloads available from
• http//www.services2.co.nz within a week
• Also available from http//www.dot.net.nz within
  a week after the event.
• Email ulrich.roxburgh_at_services2.co.nz
• Blog / Web Site http//www.services2.co.nz