Cross-Microservice Query Translation for Independent Services

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Managing dependencies among microservices in complex software applications that interoperate together or share data is challenging, particularly in optimizing queries across different microservices without sacrificing the benefits of independent operation and development.

Innovation Solution

An object service framework that supports loosely-coupled microservices, enabling them to interact through public APIs, and automatically transforms queries into optimized single database queries, while allowing each microservice to evolve independently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If microservices operate independently with separate data models and databases, then microservice independence and ease of deployment are improved, but query performance and data interoperability deteriorate

Engineering Contradiction:

Improvemicroservice independenceVSAvoidquery performance

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent introduces a query translation layer that acts as an intermediary between the client and multiple microservice databases. This layer translates high-level queries into optimized queries that can efficiently access data across independent microservice databases, thereby maintaining microservice independence while improving query performance through centralized query optimization.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a universal query interface that can handle queries across multiple independent microservices through a single entry point. This multi-functional interface provides both the independence of separate microservices and the performance of unified query processing by routing and optimizing queries across the distributed system.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If microservices share data and interoperate, then functionality and data access are improved, but system complexity and dependency management worsen

Engineering Contradiction:

Improvedata interoperabilityVSAvoiddependency management

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the system into independent microservices that each manage their own data, while introducing a separate query translation layer that handles the complexity of data interoperability. This segmentation allows microservices to remain simple and independent while the translation layer manages the complexity of cross-service queries and dependencies.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The query translation layer serves as an intermediary that manages dependencies between microservices by translating high-level queries into coordinated access patterns across multiple services. This intermediary abstracts the complexity of dependency management from individual microservices while enabling full data interoperability.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Adaptability or versatility

If multiple separate queries are executed across microservices, then microservice independence is maintained, but execution time and resource consumption increase

Engineering Contradiction:

Improvemicroservice independenceVSAvoidquery execution time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-compiling and caching query execution plans in the translation layer. When queries are received, the system can quickly retrieve pre-planned execution strategies that optimize data access across microservices, significantly reducing query execution time while maintaining microservice independence.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent merges multiple separate queries into a single optimized query execution plan through the translation layer. By combining and coordinating access to multiple microservice databases in a single optimized operation, the system reduces the total execution time compared to sequential separate queries while preserving microservice boundaries.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS20250252103A1System and method for providing cross-microservice query optimization

Publication Date: 2025.08.07 ORACLE INT CORP

AI summary

In accordance with an embodiment, described herein is a system and method for providing cross-microservice query processing. The system provides an object service framework that supports the use of microservices that may be loosely-coupled but related in some way, for example in that they interoperate together or require access to each other's data in order to process queries. Each microservice can be developed, deployed and evolve independently, and interact with the other microservices through contracts or interfaces that are defined as public APIs and are then exposed via the framework. The object service framework can be used, for example to provide a cross-microservice layer that automatically transforms queries that join objects in different microservices into a single database query that is optimized for use with the database.