17968222. SYSTEM AND METHOD FOR SUPPORTING HIGH AVAILABILITY BY USING IN-MEMORY CACHE AS A DATABASE simplified abstract (Oracle International Corporation)

From WikiPatents
Revision as of 06:26, 26 April 2024 by Wikipatents (talk | contribs) (Creating a new page)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

SYSTEM AND METHOD FOR SUPPORTING HIGH AVAILABILITY BY USING IN-MEMORY CACHE AS A DATABASE

Organization Name

Oracle International Corporation

Inventor(s)

Anurag Anand Sinha of Gorakhpur (IN)

Prakhar Rastogi of Moradabad (IN)

Harish Kumar Dalmia of Bengaluru (IN)

SYSTEM AND METHOD FOR SUPPORTING HIGH AVAILABILITY BY USING IN-MEMORY CACHE AS A DATABASE - A simplified explanation of the abstract

This abstract first appeared for US patent application 17968222 titled 'SYSTEM AND METHOD FOR SUPPORTING HIGH AVAILABILITY BY USING IN-MEMORY CACHE AS A DATABASE

Simplified Explanation

The abstract describes a system that supports high availability by using an in-memory cache as a database. The system pre-populates a subset of data from a remote database into the in-memory cache, which can act as a backup database in case the remote database goes offline.

  • The system includes an application server with an in-memory cache that pre-populates a subset of data from a remote database.
  • The in-memory cache can act as a backup database when the remote database is offline.
  • Data requests are redirected to the in-memory cache when the remote database is offline.

Potential Applications

This technology could be applied in various industries where high availability of data is crucial, such as finance, healthcare, and e-commerce.

Problems Solved

This technology solves the problem of downtime caused by database failures, ensuring continuous access to critical data.

Benefits

The use of an in-memory cache as a backup database improves system reliability and reduces the risk of data loss during database outages.

Potential Commercial Applications

This technology could be valuable for companies that require uninterrupted access to data, such as online retailers, financial institutions, and healthcare providers.

Possible Prior Art

One possible prior art could be the use of redundant databases for high availability, but the specific implementation of using an in-memory cache as a backup database may be a novel approach.

What are the specific technical details of how the system predicts which data will be accessed by the application server?

The abstract does not provide specific details on how the system predicts which data will be accessed by the application server. This aspect of the technology would be crucial in optimizing the performance of the system and ensuring efficient use of the in-memory cache.

How does the system handle data consistency between the remote database and the in-memory cache when the remote database goes offline?

The abstract does not mention how the system handles data consistency between the remote database and the in-memory cache when the remote database goes offline. Ensuring data consistency in such scenarios is essential to prevent data corruption or loss.


Original Abstract Submitted

Systems, methods, and other embodiments for supporting high availability by using in-memory cache as a database are disclosed. In one embodiment, a system includes an application server that is configured to select a sub-set of data from a remote database that is predicted to be accessed by an application server, wherein the application server includes an in-memory cache. The sub-set of data is reformatted to reduce the size. The in-memory cache is configured to act as a backup database by pre-populating the reformatted sub-set of data into the in-memory cache. In response to detecting the remote database is in an off-line state: the in-memory cache is assigned as a primary database to replace the remote database and subsequent data requests are re-directed from being processed using the remote database to being processed using the in-memory cache.