Hybrid Cloud Bridging Mainframes with Dynamic Workload Provisioning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems for bridging Systems of Record (SoRs) and Systems of Engagement (SoEs) lack the ability to dynamically provision new workloads and integrate mainframe data into hybrid clouds, relying on user-created APIs and failing to utilize mainframe capabilities effectively.
Innovation Solution
A System of Interaction (SoI) with an API-based environment and cognitive engine that maps APIs, uses a data dictionary for both SoRs and SoEs, and integrates brokerage services to create a dynamic bridge between legacy systems and cloud applications, utilizing Software Defined Networking and Queued Direct Input Output to reduce performance bottlenecks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If user-created APIs are used to bridge SoRs and SoEs, then connectivity between systems is achieved, but system complexity increases and mainframe capabilities are not effectively utilized
Solution Approach 1:
The patent introduces a System of Interaction (SoI) as an intermediary layer between Systems of Record (SoRs) and Systems of Engagement (SoEs). This SoI includes standardized API frameworks and integration services that mediate communication, reducing the need for custom user-created APIs while maintaining connectivity. The intermediary manages the complexity internally, exposing simplified interfaces to users.
Solution Approach 2:
The patent implements universal integration frameworks and standardized API templates that can be applied across multiple SoR and SoE combinations. Instead of creating unique APIs for each system pair, the universal framework provides reusable integration patterns, reducing overall system complexity while maintaining adaptability to different scenarios.
2Adaptability or versatility
If traditional bridging methods are used, then system integration is achieved, but dynamic workload provisioning and mainframe data integration into hybrid clouds are not supported
Solution Approach 1:
The patent implements dynamic workload provisioning capabilities that allow workloads to be created, modified, and deployed in real-time based on demand. The system uses automated service catalogs and orchestration mechanisms that dynamically allocate resources between SoRs and SoEs, enabling flexible workload management rather than static pre-configured connections.
Solution Approach 2:
The patent introduces self-service automation where the integration system automatically discovers available components, selects appropriate connection patterns, and provisions workloads without requiring manual user configuration. The system uses automated service catalogs and intelligent routing to enable self-service integration, improving productivity while maintaining comprehensive system integration.
3Loss of information
If mainframe systems are integrated into hybrid clouds, then data accessibility is improved, but performance bottlenecks occur due to network and I/O constraints
Solution Approach 1:
The patent replaces traditional mechanical network I/O pathways with advanced communication protocols and data transmission mechanisms. Specifically, it implements optimized data flow paths that substitute conventional network bottlenecks with high-speed communication channels and intelligent data routing, maintaining data accessibility while improving performance.
Solution Approach 2:
The patent segments data flow into multiple parallel channels and uses load balancing to distribute traffic across available pathways. By dividing the data transmission into segmented streams that can be processed concurrently through different routes, the system maintains full data accessibility while eliminating single-point performance bottlenecks.
Data Source
AI summary
Systems and methods for dynamically bridging between Systems of Record and Systems of Engagement are disclosed, including: receiving a request to provision a new workload in a distributed computing environment; identifying a plurality of components available in a system of record (SoR); receiving a selected component of at least one of the plurality of components available in the SoR; and provisioning the new workload by creating a data flow using the selected component.