Integration Landscape¶
The scenarios that support data integration can be categorised broadly into three fundamental needs:
- Accessing data – making information available to users in response to a query so that they can make the right business decisions.
- Business process step – ensuring that the correct input data is made available to a step in a process flow to allow that step to complete and create the correct output data for the next step in the flow.
- Event Trigger – where for example, a business event results in a change of some data, and that change needs to be distributed / shared with other applications or users to ensure consistency across the enterprise; thus reducing exceptions that could have occurred due to incorrect data.
Each of these scenarios or categories can be facilitated in a common consistent way – a pattern for making the right information being available in the right format at the right time. An integration pattern is a style of integration that needs to be adopted in order to satisfy the specific requirement for exchanging information between applications.
Glossary of abbreviations¶
- A2P - Application to Process
- B2B - Business to Business
- H2H - Hosted to Hosted
- H2P - Hosted to On-premise
- P2M - Process to Monitoring
- S2S - System to System
- SC - Scenario
Acknowledgements¶
- This documentation was imagined and written by Kiritkumar Mistry and is an original work. The text is not written or modified by AI.
- This documentation was created and formatted by Stephen Inglis and the integration hub team with a bit of help from AI.