Database Proxy Object Delivery for Zero-Downtime Upgrades

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In-memory databases introduce new features and data formats that require frequent updates in ABAP, making it impractical to redesign the system to natively support each new version, and existing solutions do not effectively manage cross-schema dependencies in a conflict-free manner during upgrades.

Innovation Solution

A database proxy object delivery infrastructure is implemented, which defines a dependency model between objects managed by different infrastructures, allowing for top-level management of cross-schema dependencies through logical and physical schema mapping, enabling zero-downtime upgrades by orchestrating container dependencies and deploying objects in a cycle-free sequence.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If ABAP is updated to natively support new features and data formats in each new version of in-memory database, then the system can utilize new capabilities, but the complexity and effort of redesign increases significantly

Engineering Contradiction:
Improvesupport for new in-memory database featuresVSAvoidABAP redesign complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a proxy object as an intermediary layer between the ABAP application layer and the in-memory database. This proxy object handles the complexity of new database features and data formats, allowing ABAP to interact with standardized interfaces while the proxy translates and manages the database-specific implementations. This resolves the contradiction by maintaining ABAP stability while enabling database feature adoption.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system separates the database management functionality into distinct proxy objects that can be independently updated and managed. Each proxy object encapsulates specific database operations and features, allowing granular updates without requiring comprehensive ABAP redesign. This segmentation enables incremental adaptation to new database features while maintaining overall system stability.

Inventive Principle:
Principle #1Segmentation

2Speed

If traditional relational database storage is used, then ABAP data types remain stable, but access speed is limited compared to in-memory databases

Engineering Contradiction:
Improvedata access speedVSAvoidstorage infrastructure complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent creates proxy objects that replicate the functionality of traditional database operations while operating in the in-memory environment. These proxy objects serve as virtual copies of traditional database interfaces, allowing applications to interact with in-memory storage through familiar ABAP data types and operations, thereby achieving high-speed access without compromising interface stability.

Inventive Principle:
Principle #26Copying

3Reliability

If cross-schema dependencies are managed without a formal model, then implementation is simpler, but conflicts and errors occur during upgrades

Engineering Contradiction:
Improveupgrade success rateVSAvoiddependency management infrastructure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a dependency model that pre-analyzes and records cross-schema relationships before upgrades occur. This preliminary mapping of dependencies allows the system to automatically detect potential conflicts and plan upgrade sequences in advance, ensuring reliable upgrades without requiring complex real-time conflict resolution mechanisms during the upgrade process itself.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3321797B1Database proxy object delivery infrastructure
Publication Date: 2021.06.16 SAP SE
  • EP3321797B1 patent drawingFigure 1
  • EP3321797B1 patent drawingFigure 2
  • EP3321797B1 patent drawingFigure 3

AI summary

In an example embodiment, a proxy object is delivered to a first schema having a first logical name and stored in the software object database, the proxy object referencing an object in a second schema having a second logical name. Any dependencies from the object in the second schema to the proxy object in the first schema are removed a cycle-free graph of dependencies between objects the software object database is generated. Objects are delivered the software object database using the cycle-free graph. A definition for the proxy object is created including the logical name for the first schema. The proxy object is delivered by replacing, at a time subsequent to the proxy object being delivered to the software object database, the logical name for the first schema stored in the definition with a physical name for the first schema.