Distributed Query Engine for Legacy Microservice Data Aggregation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In supply chain or procurement systems, aggregating data from multiple micro-services and legacy applications is challenging due to inflexible API access, requiring numerous customized APIs and leading to an unmanageable number of APIs that need to be exposed, monitored, and metered, with limited flexibility for users to retrieve data in various formats.
Innovation Solution
A distributed query engine is implemented to aggregate data from micro-services and legacy applications, using dedicated connectors to convert user queries into sub-queries that can be executed across various data sources, allowing for flexible and standards-compliant data extraction through REST APIs or other interfaces, enabling users to retrieve data without needing new APIs for different queries.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If customized APIs are created for each data retrieval scenario, then users can access data in various formats, but the number of APIs increases uncontrollably
Solution Approach 1:
The patent implements a universal query engine that can handle multiple data retrieval scenarios through a single standardized interface. The query engine accepts standard SQL queries and automatically routes them to appropriate microservices, eliminating the need for multiple customized APIs while maintaining data retrieval flexibility across different formats and sources
2Ease of operation
If multiple customized APIs are exposed, then specific data access needs are met, but the management and monitoring burden increases
Solution Approach 1:
The patent consolidates multiple API management functions into a single query engine that handles routing, authentication, and data retrieval through one standardized interface. This merging reduces the management overhead by eliminating the need to separately monitor and maintain multiple customized APIs while preserving comprehensive data access capabilities
3Productivity
If dedicated connectors are created for each microservice, then data aggregation from multiple sources is achieved, but the system complexity increases
Solution Approach 1:
The patent introduces a centralized query engine as an intermediary that manages connections to multiple microservices. Instead of creating dedicated connectors for each microservice, the query engine provides a unified interface that automatically routes queries to the appropriate services, reducing connector management complexity while maintaining comprehensive data aggregation capabilities
4Device complexity
If inflexible API access is used, then implementation is simpler, but user flexibility to retrieve data in various formats is limited
Solution Approach 1:
The patent enables flexible data retrieval through parameter-based query construction. The query engine accepts standard SQL queries with configurable parameters that allow users to specify different data formats, filters, and retrieval criteria without changing the underlying API structure. This maintains implementation simplicity while providing extensive data format flexibility through parameter variations
Data Source
AI summary
A distributed query engine is provided to aggregate data from and/or query a plurality of micro-services and legacy applications in multi-tenanted system in an extensible, flexible, and standards-compliant way. A plurality of dedicated connectors is provided in the distributed query engine, each providing a defined and dedicated access point to a corresponding micro-service or legacy application. A database store or database management system is associated with a corresponding one of the micro-services or the legacy applications. When a user communicates a query to the distributed query engine via a web user interface or gateway, the distributed query engine identifies one or more of the micro-services and/or legacy applications relevant to fulfilling the query, and converts the query into sub-queries, which are accordingly directed to the micro-services and/or the legacy applications to handle respective sub-queries.