Dynamic Microservice Provisioning Platform for Cloud Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing cloud platform integration (CPI) systems face challenges in securely, automatically, and efficiently provisioning microservice-based integration services, particularly due to manual errors introduced during the creation and instantiation of services, which can lead to service provisioning failures.
Innovation Solution
A provisioning application platform that automatically and dynamically instantiates and subscribes integration services on demand during both provisioning and consumption processes, utilizing model integration content from integration developers and leveraging a cloud controller for seamless subscription management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual service creation and instantiation is performed prior to provisioning, then service provisioning can be completed, but multiple errors are introduced and service provisioning failure occurs
Solution Approach 1:
The system enables self-service automation where the service creator automatically instantiates integration services during the provisioning process without requiring manual intervention. The service creator receives a provisioning request, determines required integration services, and automatically creates and subscribes them, eliminating human error while maintaining high reliability
Solution Approach 2:
The system performs preliminary determination of integration services before actual provisioning executes. The service creator identifies and prepares all required integration services, dependencies, and configurations in advance, ensuring everything is ready before the provisioning process begins, which prevents errors during execution
2Ease of manufacture
If manual service creation steps are performed before provisioning, then services can be instantiated, but the process becomes complex and error-prone
Solution Approach 1:
The system merges the service creation, instantiation, and subscription steps into a single integrated provisioning process. The service creator combines multiple previously separate operations into one automated workflow that receives a provisioning request and completes all necessary service creations and subscriptions in sequence, simplifying the overall process
Solution Approach 2:
The service creator is designed as a universal component that handles multiple functions: receiving provisioning requests, determining required integration services, instantiating services, managing subscriptions, and handling dependencies. This multi-functional approach eliminates the need for separate manual steps for each operation
3Productivity
If dynamic service instantiation is implemented during provisioning, then automation and efficiency are improved, but system complexity increases
Solution Approach 1:
The service creator acts as an intermediary component between the provisioning system and integration services. It mediates the complex interactions by receiving provisioning requests, determining service requirements, coordinating with the integration service registry, managing subscriptions, and handling dependencies, thereby simplifying the overall system architecture while enabling dynamic service instantiation
Data Source
AI summary
According to some embodiments, methods and systems may be associated with a microservice-based cloud computing environment. Model integration content may be received from an integration developer in connection with the cloud computing environment and at least one integration service may be determined associated with the received model integration content. A provisioning application platform may then automatically and dynamically instantiate the at least one integration service on demand during a provisioning process. Moreover, the provisioning application platform may also automatically subscribe the at least one integration service during the provisioning process. Similarly, at least one integration service to be consumed for received model integration content may be determined. The provisioning platform may then automatically instantiate that at least one integration service on demand during a consumption process. In this case, the provisioning application might automatically subscribe the at least one integration service during the consumption process.