Cloud Discovery Software for Rapid Service Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Integrating new cloud services into a remote network management platform is challenging, requiring custom software development and rigorous testing, which can take weeks or months, hindering the ability of enterprises to quickly adopt new cloud services and operations.
Innovation Solution
A customizable workflow within the remote network management platform allows for automatic discovery and interaction with cloud services, where updates can be made via a graphical user interface without the need for additional software updates, enabling rapid support for new cloud services by updating specifications and restructuring workflows.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If custom software development is used to integrate new cloud services into the remote network management platform, then the integration is reliable and functional, but the development time and complexity increase significantly
Solution Approach 1:
The integration process is segmented into distinct components: a standardized interface layer, a workflow engine, and cloud service-specific adapters. This allows the core platform to remain unchanged while new services are added through separate, modular components that can be developed and tested independently, reducing overall development time while maintaining reliability.
Solution Approach 2:
A standardized interface layer acts as an intermediary between the remote network management platform and various cloud services. This mediator translates diverse cloud service APIs into a unified internal format, allowing new services to be integrated without modifying the core platform, thereby reducing development complexity and time while ensuring reliable integration.
2Reliability
If custom software development is performed for each new cloud service, then the service integration is thorough and reliable, but the device complexity and development effort increase
Solution Approach 1:
The platform implements a universal workflow engine and standardized interface that can handle multiple cloud services through a single codebase. This multi-functional approach allows the same infrastructure to support diverse cloud services, reducing platform complexity while maintaining thorough integration through proven, reusable components.
Solution Approach 2:
The system uses configurable parameters and metadata to adapt to different cloud services without changing the underlying code. By parameterizing service-specific behaviors, authentication methods, and API mappings, the platform maintains low complexity while achieving reliable, thorough integration across multiple services through configuration rather than code changes.
3Reliability
If rigorous testing is performed during the development process, then the integration reliability is ensured, but the development timeline is extended
Solution Approach 1:
The system performs preliminary actions by implementing automated testing frameworks and validation rules before full integration is completed. Configuration schemas validate service definitions upfront, and the workflow engine includes built-in error handling and rollback mechanisms, ensuring reliability is built-in from the start rather than added through extended testing, thus maintaining both reliability and productivity.
4Reliability
If the platform maintains pre-configured interfaces for cloud services in application code, then the integration is stable and reliable, but the adaptability to new services is reduced
Solution Approach 1:
The system transitions from static, hard-coded interfaces to dynamic, configurable interfaces. The workflow engine reads service definitions from external configuration files or databases, allowing the system to adapt to new cloud services dynamically without code changes. This maintains stability through the proven workflow engine while achieving versatility through flexible, data-driven service definitions.
Data Source
AI summary
A computational instance of a remote network management platform may be dedicated to a managed network. The managed network may use computing resources of a cloud-based service provider. One or more processors may be disposed within the computational instance and may cause a provider-neutral cloud discovery software application to: (i) obtain a specification that defines an interface for accessing the cloud-based service provider, a discoverable set of computing resources provided by the cloud-based service provider, and mappings between descriptions of the discoverable set of computing resources and the database tables disposed within the computational instance, (ii) log on to the cloud-based service provider by way of the interface, (iii) request and receive, from the cloud-based service provider, descriptions of the discoverable set of computing resources, and (iv) store, in fields of database tables, the descriptions of the discoverable set of computing resources in accordance with the mappings.