About

In the organization we have chosen to use Microsoft Azure Integration Services to implement out iPaaS platform which is used to integrate systems in the cloud and systems on premise where integration between systems is needed to facilitate an end to end business process.

The below diagram shows a high level view of our integration platform at a capability to resource mapping perspective.

Key Points to Note:

• We use Logic Apps for orchestration and connectivity to many systems

• Where an application is API enabled we will attempt to use API Management as a proxy to that API for centralized management

• We prefer event and message based patterns where possible to allow us to build publish/subscribe architectures which support plug and play interfaces which give us maximum flexibility to be agile at an architecture and delivery perspective

• We prefer not to use point-to-point integrations without an architecture exception

• We can use batch based integrations if needed

• We can connect to on-premise applications via network integration for Logic Apps and API Management

• In bulk data shifting scenarios like ETL/ELT we can use Data Factory/Synapse

• We compliment the out of the box Azure capabilities with Turbo360 to help us get the last mile to give an excellent monitoring and management experience and to allow L1 and L2 support operators to help run the integration platform

• Costs are managed with Turbo360 to ensure we can easily ensure the platform is cost efficient