Klevr Integration Hub

• All integrations are composed of small “workflow definitions” which are joined via a pub/sub model.
  • Inbound workflows;
  • Transform workflows;
  • Routing workflows;
  • Outbound workflows.
• These workflows are easily joined together to make complex integration requirements quick and easy to build.
• What’s more, workflows are not “hand written” – every workflow type has a small, simple to use workflow definition file.
• So, to create an integration we:
  • Define the overall integration (inbound workflow, any transform and routing required, and the outbound workflow).
  • Create the small definition files needed – anywhere from two to a dozen or so (for really, really complex integrations).
  • Commit the definition files to Azure DevOps.
• And that’s it! The Klevr Integration Hub deployment system deploys everything needed – the infrastructure and the integration, ready to go.

AZURE SERVICES

Solution Overview

Klevr Integration Hub enforces the implementation of integration best practices and automates the build and deployment of native Azure services (via Azure DevOps) so there is no operational lock-in to a proprietary integration technology framework.

The native Azure services that are automatically built and deployed include, but are not limited to:

• API Management
• Logic App Connectors and Workflows
• Function Apps and App Service Plans
• Service Bus
• Event Grid Subscriptions
• Blob Storage
• Application Insights and Alerts