Integration Discovery Service for Cloud Application Automation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional cloud platforms lack the ability to automatically integrate software applications deployed on them, forcing customers to manually integrate services, which is error-prone and exposes sensitive technical details.
Innovation Solution
A cloud platform that automatically integrates different software applications by using a multitenancy architecture, life cycle management service, and integration discovery service to register tenants, create schemas, and establish APIs, endpoints, and security settings, enabling seamless integration between calling and called applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If customers manually integrate software applications on cloud platform, then integration capability is achieved, but error rate increases and sensitive details are exposed
Solution Approach 1:
The system enables self-service integration by automatically discovering applications, generating integration configurations, and establishing connections without manual intervention. The integration discovery service autonomously performs schema registration, API endpoint discovery, and security configuration, allowing the system to integrate applications itself rather than requiring customer expertise.
Solution Approach 2:
The integration discovery service acts as an intermediary between applications on the cloud platform, facilitating automatic integration. It discovers application schemas, generates integration configurations, and manages the integration process, thereby shielding customers from sensitive technical details while maintaining reliable integration.
2Ease of operation
If cloud provider handles system administration, then customer focus on services improves, but application integration capability is lost
Solution Approach 1:
The cloud platform provides multi-functionality by combining system administration management with application integration capabilities. The integration discovery service enables the platform to both manage infrastructure (handled by cloud provider) and facilitate application integration (new capability), allowing customers to consume services easily while also integrating applications when needed.
Solution Approach 2:
The integration discovery service serves as a new intermediary layer that enables application integration without requiring customers to perform system administration. It sits between the cloud provider's infrastructure management and customer application integration needs, providing automated integration capabilities while maintaining the division of responsibilities.
3Reliability
If automatic integration is implemented, then error rate decreases, but system complexity increases
Solution Approach 1:
The integration discovery service acts as a specialized intermediary component that handles the complexity of automatic integration. It discovers application schemas, generates integration configurations, and manages connections between applications, thereby reducing errors while containing system complexity within a dedicated service rather than distributing it throughout the entire platform.
Solution Approach 2:
The system segments integration functionality into a separate integration discovery service rather than embedding it throughout the entire cloud platform. This modular approach allows automatic integration capabilities to be developed and maintained independently, reducing overall system complexity while improving integration accuracy through specialized functionality.
Data Source
AI summary
Disclosed herein are system, method, and computer program product embodiments for automatically integrating different software applications in a cloud platform. An embodiment operates by creating a registration entry representing an integration use-case for a first tenant of a first application in an integration discovery service. The embodiment generates a barcode based on the registration entry. The embodiment matches the integration use-case for the first tenant of the first application with a potential integration use-case for a second tenant of a second application based on the barcode. The embodiment then creates an integration configuration for enabling the integration use-case for the first tenant of the first application with the potential integration use-case for the second tenant of the second application based on the matching.


