Multi-Tenant Microservices Framework for Consistent Cache Behavior

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Developing consistent multi-tenant behavior in microservices-based applications is challenging due to the need for each microservice to handle requests and operations for different tenants, which often requires significant time and resources, and modifying microservices to function in arbitrary application contexts is prohibitive.

Innovation Solution

A multi-tenant framework is introduced that includes modules and software components to handle tenant context data extraction, caching, and circuit breaking, allowing microservices to operate in a tenant-agnostic manner, ensuring consistent behavior across the distributed computing system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If microservices are modified to handle tenant context data manually, then multi-tenant functionality can be achieved, but development time and complexity increase significantly

Engineering Contradiction:
Improvemulti-tenant functionalityVSAvoiddevelopment complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a multi-tenant framework as an intermediary layer between microservices and tenant context data. This framework automatically extracts, caches, and manages tenant context data, eliminating the need for each microservice to implement manual tenant handling logic. The framework acts as a mediator that transparently handles multi-tenant requirements while keeping microservices simple and focused on their core functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If each microservice implements its own tenant context handling, then tenant-specific operations can be performed, but computational overhead and resource consumption increase

Engineering Contradiction:
Improvetenant-specific operationsVSAvoidcomputational overhead
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent implements a caching mechanism that performs preliminary action by extracting and storing tenant context data in advance. When a microservice needs tenant context information, it is retrieved from the cache rather than being re-extracted and re-processed. This preliminary caching action significantly reduces computational overhead and resource consumption while enabling tenant-specific operations across multiple microservices.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If microservices are designed to be lightweight and independent, then system flexibility and deployability improve, but consistent multi-tenant behavior across services becomes difficult to maintain

Engineering Contradiction:
ImprovedeployabilityVSAvoidbehavior consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent creates a universal multi-tenant framework that can be applied across all microservices in the system. This framework provides consistent tenant context extraction, caching, and management functionality that works uniformly across different microservices regardless of their specific purposes. The universal framework ensures behavior consistency while allowing each microservice to remain lightweight and independently deployable.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS12524280B2Techniques for consistent multi-tenant behavior in microservices based applications
Publication Date: 2026.01.13 ORACLE INT CORP
  • US12524280B2 patent drawing
  • US12524280B2 patent drawing
  • US12524280B2 patent drawing

AI summary

Techniques are disclosed for using a multi-tenant framework for microservices in a microservices-based application to implement a tenant-aware distributed cache. The microservices-based application can include at least one microservice that incorporates the multi-tenant framework. The multi-tenant framework includes software components configured to provide multi-tenant functionality for the microservice. A microservice may receive first request associated with a tenant and comprising tenant context data. A first software component of the multi-tenant framework can extract the tenant context data from the request. The microservice can receive a second request comprising request data. A second software component of the multi-tenant framework can use the tenant context data to store the request data in a cache.