Integration Patterns – Part A

Pattern Numbers

Name

Characteristics

   1

Source Standard Interface (event driven)

• Real-Time from source to middleware

• No response sent back from middleware

Source Standard Interface (batch)

• Batch from source to middleware
• No response sent back from middleware

Source Asynchronous Request Reply (event driven)

• Real-Time from source to middleware
• Non-immediate response from middleware
• (Any responses sent back from target system are considered a separate interface)

Source Asynchronous Request Reply (batch)

• Batch from source to middleware
• Non-immediate response from middleware
• (Any responses sent back from target system are considered a separate interface)

Source Synchronous Request Reply (event driven)

• Real-Time from source to middleware
• Immediate response from middleware

Source Synchronous Request Reply (batch)

• Batch from source to middleware
• Immediate response from middleware

Target Standard Interface (event driven)

• Real-Time from middleware to target
• No response sent back from target

Target Standard Interface (batch)

• Batch from middleware to target
• Individual transactions are combined into a batch
• Scheduler sends batch to target
• No response sent back from target

Target Asynchronous Request Reply (event driven)

• Real-Time from middleware to target
• Non-immediate response from target
• (Any responses sent back from target system are considered a separate interface)

Target Asynchronous Request Reply (batch)

• Batch from middleware to target
• Individual transactions are combined into a batch
• Scheduler sends batch to target
• Non-immediate response from target
• (Any responses sent back from target system are considered a separate interface)

Target Synchronous Request Reply (event driven)

• Real-Time from middleware to target
• Immediate response from target

Target Synchronous Request Reply (batch)

• Batch from middleware to target
• Individual transactions are combined into a batch
• Scheduler sends batch to target
• Immediate response from target

Point-to-Point Standard Interface (source=event driven, target=event driven)

• Data is going to only one target system for the life of the business object
• Real-Time from source to target
• No response sent back from target

Point-to-Point Standard Interface (source=batch, target=event driven)

• Data is going to only one target system for the life of the business object
• Batch from source to middleware
• Event from middleware to target
• The unit of work can be the entire batch (I.e. if one transaction fails the entire batch needs to fail – common in financial transactions)
• The unit of work can be each individual transaction
• No response sent back from target

Point-to-Point Standard Interface (source=event driven, target=batch)

• Data is going to only one target system for the life of the business object
• Event from source to middleware
• Batch from middleware to target
• The unit of work can be the entire batch (I.e. if one transaction fails the entire batch needs to fail – common in financial transactions)
• The unit of work can be each individual transaction
• No response sent back from target

Point-to-Point Standard Interface (source=batch, target=batch)

• Data is going to only one target system for the life of the business object
• Batch from source to middleware
• Batch from middleware to target
• The unit of work can be the entire batch (I.e. if one transaction fails the entire batch needs to fail – common in financial transactions)
• The unit of work can be each individual transaction
• No response sent back from target

Point-to-Point Asynchronous Request Reply (source=event driven, target=event driven)

• Data is going to only one target system for the life of the business object.
• Real-Time from source to target
• Non-immediate response sent back from target

Point-to-Point Asynchronous Request Reply (source=batch, target=event driven)

• Data is going to only one target system for the life of the business object
• Batch from source to middleware
• Event from middleware to target
• The unit of work can be the entire batch (I.e. if one transaction fails the entire batch needs to fail – common in financial transactions)
• The unit of work can be each individual transaction
• Non-immediate response sent back from target

Point-to-Point Asynchronous Request Reply (source=event driven, target=batch)

• Data is going to only one target system for the life of the business object
• Event from source to middleware
• Batch from middleware to target
• The unit of work can be the entire batch (I.e. if one transaction fails the entire batch needs to fail – common in financial transactions)
• The unit of work can be each individual transaction
• Non-immediate response sent back from target

Point-to-Point Asynchronous Request Reply (source=batch, target=batch)

• Data is going to only one target system for the life of the business object
• Batch from source to middleware
• Batch from middleware to target
• The unit of work can be the entire batch (I.e. if one transaction fails the entire batch needs to fail – common in financial transactions)
• The unit of work can be each individual transaction
• Non-immediate response sent back from target

Point-to-Point Synchronous Request Reply (event driven)

• Data is going to only one target system for the life of the business object
• Real-Time from source to target
• Immediate response sent back from target

Point-to-Point Synchronous Request Reply (batch)

• Data is going to only one target system for the life of the business object
• Batch from source to middleware
• Batch from middleware to target
• The unit of work can be the entire batch (I.e. if one transaction fails the entire batch needs to fail – common in financial transactions)
• Immediate response sent back from target