Composable Query Gateway Routing Microservices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In conventional microservice architectures, clients must transmit separate queries to multiple services and manually aggregate results, leading to a tedious, time-consuming, and error-prone process, especially for applications using large numbers of services.

Innovation Solution

A composable query language gateway protocol generates a query routing data structure based on service schemas, allowing clients to send queries to the appropriate services and aggregate results efficiently, eliminating the need for manual data compilation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If clients transmit separate queries to multiple services and manually aggregate results, then each service can be independently queried, but the process becomes tedious, time-consuming, and error-prone

Engineering Contradiction:
Improvequery flexibilityVSAvoidmanual aggregation effort
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces a gateway as an intermediary component that receives client queries, automatically routes them to the appropriate services, and aggregates the results. This mediator eliminates the need for clients to manually manage multiple service queries and result aggregation, resolving the contradiction between query flexibility and operational ease.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If clients manually compile results from multiple services, then data from all services can be obtained, but the process is time-consuming and error-prone

Engineering Contradiction:
Improvedata completenessVSAvoidmanual compilation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The gateway performs preliminary actions by pre-establishing service schemas, identifying service types, and creating query routing data structures in advance. When a client query arrives, the gateway already has the routing information ready, enabling automatic and efficient result aggregation without manual intervention, thus reducing time loss while maintaining data completeness.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If separate queries are sent to each service, then specific service data can be retrieved, but the overall process becomes complex and error-prone

Engineering Contradiction:
Improvedata retrieval efficiencyVSAvoidquery management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent merges the functions of multiple service queries and result aggregations into a single gateway component. The gateway consolidates query routing, service communication, and result compilation into one unified system, reducing query management complexity while maintaining or improving data retrieval efficiency through automated processes.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS11886394B2Composable query language gateway routing protocol
Publication Date: 2024.01.30 RED HAT INC
  • US11886394B2 patent drawing
  • US11886394B2 patent drawing
  • US11886394B2 patent drawing

AI summary

A query request for data associated with a plurality of services executed by a plurality of host systems is received. A type of query associated with the query request is identified. A subset of the plurality of services comprising data associated with the type of query is identified using a query routing data structure, wherein the query routing data structure is received from a gateway system that generates the query routing data structure in view of receiving corresponding service schemas from the plurality of services. The query request is transmitted to the subset of the plurality of services identified using the query routing data structure.