Gateway Hyper-Memory In-Memory Database Architecture

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing gateways face limitations in query time due to reliance on older relational database technology and methods, leading to performance bottlenecks from disk input-output rates and network latency, and scalability issues with distributed caches and Java object management.

Innovation Solution

A gateway architecture incorporating an integration gateway, domain gateway, and hyper-memory portion with in-memory data storage and indexing, utilizing 64-bit technology and digital trie-based indexes to store and access large datasets entirely within memory, avoiding disk I/O and network latency, and minimizing Java object creation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If disk-based relational database technology is used for data storage, then data persistence and reliability are improved, but query resolution time deteriorates due to disk input-output rate limitations

Engineering Contradiction:

Improvedata persistenceVSAvoidquery resolution time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system segments data storage into two distinct layers: a disk-based relational database for persistent storage and a memory-based hyper-memory database for high-speed access. This segmentation allows the system to maintain data reliability on disk while achieving fast query resolution through memory access, resolving the contradiction between reliability and speed.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The hyper-memory database acts as an intermediary layer between the disk-based relational database and the gateway application. It caches frequently accessed data in memory, mediating between the slow disk I/O and the fast application requirements, thereby improving query resolution time without compromising data persistence.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Speed

If distributed caches are used to accelerate data access, then query speed is improved, but network latency is introduced and scalability becomes difficult

Engineering Contradiction:

Improvedata access speedVSAvoidnetwork latency

Core Design Contradiction:

SpeedVSLoss of time

Solution Approach 1:

The patent merges the cache functionality directly into the gateway application as an integrated hyper-memory database, rather than using separate distributed cache systems. This integration eliminates network communication overhead between the gateway and cache, reducing network latency while maintaining fast data access speed.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The in-memory hyper-memory database serves as an intermediary storage layer within the gateway itself, eliminating the need for external distributed cache systems. This removes network latency from the data access path while maintaining high-speed access through memory-resident data structures.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Adaptability or versatility

If Java objects are used in the database implementation, then object-oriented functionality is improved, but object churning occurs causing performance degradation

Engineering Contradiction:

Improveobject-oriented functionalityVSAvoidsystem performance

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The system changes the fundamental parameter of data representation from Java objects to primitive data types and structured records in the hyper-memory database. This parameter change eliminates object creation and destruction cycles, removing the performance degradation caused by object churning and garbage collection while maintaining object-oriented functionality at the application layer.

Inventive Principle:

Principle #35Parameter changes

4Device complexity

If data is stored on a separate physical server, then system modularity is improved, but network latency increases for data access

Engineering Contradiction:

Improvesystem modularityVSAvoidnetwork latency

Core Design Contradiction:

Device complexityVSLoss of time

Solution Approach 1:

The patent merges the hyper-memory database and gateway application into a single physical deployment unit. This merging eliminates network communication between separate servers for data access, removing network latency while maintaining the modular architectural benefits of separating concerns at the software layer.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS8181187B2Gateways having localized in-memory databases and business logic execution

Publication Date: 2012.05.15 CHANGE HEALTHCARE HOLDINGS LLC

AI summary

A gateway is provided that includes an integration gateway portion, a domain gateway portion, and a hyper-memory portion is provided. The integration gateway portion has an integration rules engine, a search engine, and a first virtual machine. The domain gateway portion has a domain rules engine. The hyper-memory portion has a hyper-memory engine, a hyper-memory, and a second virtual machine. The integration portion accesses a database via the integration rules engine and the first virtual machine or via the search engine and the first virtual machine. The domain gateway portion accesses datasets of the database that are resident in the hyper-memory via the domain objects rules engine and the hyper-memory engine or via the search engine, the second virtual machine, and the hyper-memory engine.