Middleware Flow Assessment for End-to-End Latency Projection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The integration of travel industry software, such as supply chain management and enterprise resource planning systems, faces challenges in communicating effectively, leading to inefficiencies like duplicate data storage and automation difficulties, due to complex development processes and lack of real-time metrics during the enterprise application integration (EAI) process.
Innovation Solution
A method and system for middleware flow assessment in EAI systems that facilitate data exchange between front-end applications, middleware web-based business services, and APIs, allowing for the compilation of complete end-to-end flows and projection of latency by totaling response times, with the option to generate sequence diagrams and utilize lookup tables for latency statistics.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If separate development teams define dependencies on a point-to-point basis or in separate isolated groups, then each team can work independently, but the development process becomes complex and difficult to integrate across teams
Solution Approach 1:
The patent segments the EAI development process into distinct layers (front-end application layer, middleware business services layer, and back-end system layer). Each layer can be developed and managed independently by separate teams, yet the layered architecture provides a unified framework for integration. The integration layer acts as an intermediary that connects these segmented components without requiring teams to manage complex point-to-point dependencies directly.
Solution Approach 2:
The patent introduces an integration layer with standardized interfaces and protocols that act as an intermediary between front-end applications and back-end systems. This intermediary layer simplifies cross-team integration by providing a common communication framework, reducing the complexity of direct point-to-point connections while maintaining independent team autonomy.
2Ease of manufacture
If EAI integration is performed without real-time metrics, then the development process can proceed without continuous monitoring, but key intermediate information such as response time projections cannot be provided
Solution Approach 1:
The patent implements continuous monitoring and assessment mechanisms that provide real-time feedback on EAI integration metrics, including response times, throughput, and system performance. This feedback enables developers to track intermediate information during the development process, allowing for response time projections and performance optimization without adding excessive complexity to the development workflow.
Solution Approach 2:
The patent enables preliminary assessment of response times and performance metrics during the design and development phases, rather than only after deployment. By incorporating monitoring tools and latency calculation capabilities into the development environment, teams can obtain response time projections and make informed decisions before full implementation, preventing information loss.
3Adaptability or versatility
If multiple applications are integrated without a standardized framework, then application independence is maintained, but communication efficiency decreases leading to duplicate data storage and automation difficulties
Solution Approach 1:
The patent implements a universal integration layer with standardized interfaces, protocols, and data formats that can accommodate multiple different applications and systems. This universal framework enables efficient communication across diverse applications while maintaining their independence. The standardized layer handles common tasks such as data transformation, protocol conversion, and error handling, improving overall communication efficiency without requiring applications to lose their individual characteristics.
Data Source
AI summary
Methods, systems, and computer program products for integrating front-end applications with application program interfaces (APIs) and middleware business services. A front-end application flow, including at least one call to one or more business services flows, and one or more business services flows, each including one or more calls to application program interfaces (APIs), are received at a processor and the processor compiles a complete end-to-end flow that includes the front-end application flow and the one or more business services flows. The complete end-to-end flow is expressed in ordered terms of the one or more business services flows and the one or more calls to the APIs. A projected latency for the complete end-to-end flow is automatically constructed by the processor by totaling response times for each of the one or more calls to the APIs included in the complete end-to-end flow.