Dynamic ORM Field Mapper Runtime Adjustment

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing object-relational mapping systems are inflexible and cannot dynamically adjust mappings during runtime without requiring system re-initialization, leading to performance issues and difficulties in supporting changing persistence layers or data migrations.

Innovation Solution

Incorporating a dynamic adjustment strategy that allows temporary or conditional mapping behaviors to be injected into field mappers, enabling real-time modifications without re-initialization, and maintaining high performance by overriding or supplementing original mapping strategies based on predefined conditions or events.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If object-relational mapping systems use static field mappers with fixed mapping strategies, then system stability and performance are maintained, but the system cannot dynamically adjust mappings during runtime without re-initialization

Engineering Contradiction:

Improvedynamic mapping adjustment capabilityVSAvoidsystem availability during runtime

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements dynamic adjustment strategies that allow field mappers to change their mapping behavior during runtime based on predefined conditions or events. The system transitions from static, fixed mappings to dynamic, condition-based mappings that can adapt without system re-initialization, resolving the contradiction between adaptability and reliability.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The patent introduces an intermediary adjustment strategy layer that sits between the persistence layer and the object-oriented domain model. This intermediary enables conditional override of mapping behaviors without disrupting the core ORM system, allowing dynamic adjustments while maintaining system stability and continuous availability.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Manufacturing precision

If object-relational mapping systems re-initialize to adjust mappings, then mapping accuracy is improved, but system performance degrades and availability is interrupted

Engineering Contradiction:

Improvemapping accuracyVSAvoidsystem performance and availability

Core Design Contradiction:

Manufacturing precisionVSProductivity

Solution Approach 1:

The patent employs preliminary action by pre-defining adjustment strategies and conditions during system initialization. These strategies are prepared in advance and can be activated during runtime without requiring re-initialization, thus maintaining mapping accuracy while preserving system performance and availability.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent ensures continuity of useful action by enabling mapping adjustments to occur during runtime without interrupting system operation. The conditional adjustment strategies allow the system to maintain continuous data access and processing while adapting mapping behaviors, eliminating the need for stopping and re-initializing the system.

Inventive Principle:

Principle #20Continuity of useful action

3Adaptability or versatility

If object-relational mapping systems support multiple application versions or data migrations, then adaptability improves, but system complexity increases

Engineering Contradiction:

Improvesupport for overlapping versions and migrationsVSAvoidsystem architecture complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies segmentation by dividing the mapping system into independent field mappers, each with its own adjustable mapping strategy. This modular approach allows individual mappers to be configured with different adjustment strategies for different application versions or data migration scenarios, enabling adaptability without proportionally increasing overall system complexity.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements universality through a common adjustment strategy framework that can handle multiple scenarios including version overlaps, data migrations, and conditional mappings. This universal framework provides a standardized mechanism for managing diverse requirements, reducing the complexity that would otherwise arise from implementing separate solutions for each scenario.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS9430504B2Systems and methods for dynamically intercepting and adjusting persistence behaviors via runtime configuration

Publication Date: 2016.08.30 BENEFITFOCUS COM INC

AI summary

The systems and methods described herein relate to dynamic runtime modifications of an object-relational mapping behavior associated with a relational persistence layer. In various embodiments, access to a relational persistence layer, such as a relational database management system may be provided via an object-relational mapper (ORM). The ORM may map data from the relational persistence layer to an object-oriented domain model. The ORM may include a plurality of field mappers configured with an original mapping strategy to map an entity field from the relational persistence layer to the object-oriented domain model. One or more of the field mappers may be configured with a dynamic adjustment strategy that allows the selected field mapper(s) to be injected with a temporary or conditional mapping behavior. The dynamic adjustment strategy may be initialized with the field mapper at startup, while the injection of temporary or conditional mappings may be performed during runtime.