Scenario-Based Database Partitioning for Elastic Scaling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database scaling methods require replicating entire databases across additional servers, leading to inefficient use of resources and performance issues, as they do not account for varying workloads across different application functionalities.

Innovation Solution

Implementing a system that replicates only subsets of application resource content associated with specific application scenarios to dedicated nodes, allowing for targeted scaling and processing of requests, thereby optimizing resource utilization and reducing overall processing time.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If entire databases are replicated across additional servers, then application scaling is achieved, but resource utilization becomes inefficient and processing time increases

Engineering Contradiction:
Improveapplication scalingVSAvoidresource utilization efficiency
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The patent segments the database into multiple partitions, each stored on a separate server. Instead of replicating entire databases across all servers, each server holds only its designated partition, enabling scalable application performance while optimizing resource utilization by eliminating redundant data storage.

Inventive Principle:
Principle #1Segmentation

2Reliability

If entire databases are replicated across additional servers, then data availability is improved, but storage costs increase

Engineering Contradiction:
Improvedata availabilityVSAvoidstorage resources
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The database is divided into partitions distributed across servers, ensuring data availability through distribution while minimizing storage requirements. Each server stores only its assigned partition rather than complete database copies, reducing total storage consumption while maintaining accessibility.

Inventive Principle:
Principle #1Segmentation

3Productivity

If entire databases are replicated across additional servers, then request processing capacity increases, but computing costs increase

Engineering Contradiction:
Improverequest processing capacityVSAvoidcomputing resources
Core Design Contradiction:
ProductivityVSUse of energy by moving object

Solution Approach 1:

By partitioning the database and distributing it across servers, the system enables parallel request processing on multiple nodes simultaneously. Each server processes requests for its specific partition, increasing overall throughput while reducing the computing burden on individual servers compared to handling complete database operations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements local quality by having each server optimized to handle specific partition operations. Servers are configured with the necessary computing resources for their assigned partitions, enabling efficient local processing without requiring every server to maintain full database processing capabilities, thus optimizing computing resource allocation.

Inventive Principle:
Principle #3Local quality

Data Source

PatentEP3182298B1Smart elastic scaling based on application scenarios
Publication Date: 2023.05.10 SAP SE
  • EP3182298B1 patent drawingFigure 1
  • EP3182298B1 patent drawingFigure 2
  • EP3182298B1 patent drawingFigure 3

AI summary

Technologies are provided for scaling applications via application scenarios. Portions of application resource content stored in a database are associated with application scenarios. The portions of the resource content associated with an application scenario are replicated to one or more computing nodes associated with the application scenario. Requests associated with the application scenario are transmitted to the one or more one or more computing nodes, where they are processed using the replicated portions of the resource content associated with the application scenario.