Adaptive User Database Mapping for Server Load Balancing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional systems for managing database resources struggle to accurately balance processing consumption across servers, often relying on random user selection or historical data, which fails to account for current usage patterns, leading to inefficient resource allocation and potential degradation of user experience.

Innovation Solution

The adaptive selection of user to database mapping, where a processing consumption model is generated based on user and database properties, allowing for behavior change suggestions and proactive user reassignment to optimize resource usage, reducing strain on overburdened servers and improving user interactivity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If random user selection is used to balance server load, then implementation simplicity is improved, but resource allocation accuracy deteriorates

Engineering Contradiction:
Improveimplementation simplicityVSAvoidresource allocation accuracy
Core Design Contradiction:
Ease of manufactureVSMeasurement precision

Solution Approach 1:

The system continuously monitors current server load metrics and user behavior patterns, using this feedback to dynamically adjust user-to-database mappings. This replaces random selection with data-driven decisions that accurately reflect current system state and user needs.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system pre-calculates optimal user mappings based on historical behavior patterns and database usage characteristics before load balancing is needed. This preliminary analysis enables accurate resource allocation when balancing occurs, rather than relying on random selection.

Inventive Principle:
Principle #10Preliminary action

2Loss of information

If historical data analysis is used for user selection, then decision basis is improved, but responsiveness to current usage patterns deteriorates

Engineering Contradiction:
Improvedecision basisVSAvoidresponsiveness to current usage
Core Design Contradiction:
Loss of informationVSSpeed

Solution Approach 1:

The system transitions from static historical analysis to dynamic load balancing that continuously adapts to current usage patterns. User-to-database mappings are adjusted in real-time based on current server load and active user behavior, making the system responsive to changing conditions.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system maintains continuous monitoring of both historical patterns and current usage, ensuring that load balancing decisions are based on an unbroken stream of relevant data. This continuous action ensures neither historical context nor current state is lost in the decision-making process.

Inventive Principle:
Principle #20Continuity of useful action

3Measurement precision

If more detailed user criteria analysis is performed, then user-to-database mapping accuracy is improved, but system complexity deteriorates

Engineering Contradiction:
Improvemapping accuracyVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system segments the load balancing decision into distinct components: user behavior analysis, database characteristics evaluation, and mapping optimization. Each component handles specific criteria independently, reducing overall system complexity while maintaining comprehensive analysis accuracy.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP3622397B1Adaptive selection of user to database mapping
Publication Date: 2025.03.26 MICROSOFT TECHNOLOGY LICENSING LLC
  • EP3622397B1 patent drawingFigure 1
  • EP3622397B1 patent drawingFigure 2A
  • EP3622397B1 patent drawingFigure 2B

AI summary

Technologies are described for adaptive selection of user to database mapping. An impact to processing resources by a user of a database managed by the processing resources may be predicted using criteria based on user - database properties such as a number of rows in database, a number of rows in database for the user, a maximum depth of hierarchy for the user, a maximum breadth of hierarchy for the user, applications that have recently accessed the user's data, distribution of quota types in the user's data, a number of shared items in the user's hierarchy, a number of people who share in the user's shared item hierarchy, an application employed by the user to access the data currently, etc. Based on a model for the predicted impact, a behavior change (for any of the criteria) and/or a move of the user to another database may be suggested / automatically implemented.