Codeless Cloud Integration via Service Specifications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Configuring a remote network management platform to interact with new cloud computing services is challenging due to distinct configuration details, requiring extensive development and integration testing, which is time-consuming and resource-intensive.
Innovation Solution
A computing-service-neutral (CSN) cloud integration application that allows remote network management platforms to easily integrate with new cloud computing services by updating a specification, eliminating the need for custom software updates, and using pagination types to handle split descriptions across multiple integration points.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If custom software is developed to incorporate distinct configuration details into the remote network management platform, then the platform can interact with new computing services, but the integration process takes weeks or months due to rigorous integration testing
Solution Approach 1:
The patent segments the integration configuration into distinct components: integration points, pagination types, and field mappings. These segmented configuration elements can be independently specified and combined, allowing rapid adaptation to new services without complete reconfiguration or extensive testing of the entire integration process.
Solution Approach 2:
The patent performs preliminary action by pre-defining integration points, pagination types, and field mappings as reusable configuration templates. When a new computing service needs to be integrated, these pre-configured elements can be selected and combined rather than created from scratch, significantly reducing integration time while maintaining adaptability.
2Adaptability or versatility
If a team of application developers creates custom software for each new computing service, then the platform gains support for new services, but the process becomes unduly time-consuming when multiple new services need to be integrated
Solution Approach 1:
The patent creates a universal configuration framework that can accommodate multiple different computing services through a common set of integration points, pagination types, and field mappings. This multi-functional approach allows the same platform infrastructure to support various services without requiring separate custom software development teams for each service, thereby increasing productivity while maintaining versatility.
Solution Approach 2:
The patent enables copying of configuration templates and patterns across different computing services. Once integration configurations are established for one service, they can be replicated and adapted for other services, eliminating the need to recreate integration logic from scratch and significantly accelerating the rate at which new services can be added.
3Reliability
If extensive integration testing is performed to ensure proper interaction with new computing services, then integration reliability is improved, but the development process takes weeks or months
Solution Approach 1:
By segmenting the integration configuration into discrete, testable components (integration points, pagination types, field mappings), the patent enables targeted testing of individual elements rather than requiring exhaustive end-to-end testing of entire integration scenarios. This segmented approach maintains reliability while reducing overall testing time.
Solution Approach 2:
The patent performs preliminary validation and configuration of integration elements before full integration testing. By pre-defining and validating integration points, pagination types, and field mappings as reusable templates, the system reduces the scope of required integration testing when deploying new services, thereby maintaining reliability with reduced testing time.
Data Source
AI summary
A computational instance may include, in database tables, representations of computing services provided by remote networks. One or more processors disposed in the computational instance may cause a computing-service-neutral cloud integration application to perform operations including: obtaining a specification related to a remote network, where the specification defines: (i) an integration point for the remote network, (ii) a pagination type associated with the integration point, and (iii) mappings between descriptions of the computing services provided by the remote network and fields of the database tables. The operations may further include requesting and receiving, via the integration point, first descriptions of the computing services; determining, from the pagination type and the integration point, a second integration point for the remote network; requesting and receiving, via the second integration point, second descriptions; and storing, in the database tables, the first descriptions and the second descriptions in accordance with the mappings.