Oracle international corporation (20240126698). SYSTEM AND METHOD FOR SUPPORTING HIGH AVAILABILITY BY USING IN-MEMORY CACHE AS A DATABASE simplified abstract
Contents
- 1 SYSTEM AND METHOD FOR SUPPORTING HIGH AVAILABILITY BY USING IN-MEMORY CACHE AS A DATABASE
- 1.1 Organization Name
- 1.2 Inventor(s)
- 1.3 SYSTEM AND METHOD FOR SUPPORTING HIGH AVAILABILITY BY USING IN-MEMORY CACHE AS A DATABASE - A simplified explanation of the abstract
- 1.4 Simplified Explanation
- 1.5 Potential Applications
- 1.6 Problems Solved
- 1.7 Benefits
- 1.8 Potential Commercial Applications
- 1.9 Possible Prior Art
- 1.10 Original Abstract Submitted
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 20240126698 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 e-commerce, banking, and healthcare.
Problems Solved
This technology solves the problem of data unavailability when the primary database goes offline, ensuring continuous access to critical information.
Benefits
The use of an in-memory cache as a backup database improves system reliability and reduces downtime, leading to better user experience and increased productivity.
Potential Commercial Applications
This technology could be valuable for companies that rely on real-time data processing and cannot afford downtime, such as financial institutions, online retailers, 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.
Unanswered Questions
How does this technology impact system performance compared to traditional backup solutions?
This article does not provide information on the performance implications of using an in-memory cache as a backup database. Further research or testing may be needed to determine the impact on system performance.
What are the potential security risks associated with using an in-memory cache as a primary database?
The article does not address the security aspects of using an in-memory cache as a primary database. It would be important to consider potential vulnerabilities and implement appropriate security measures to protect the data stored in the cache.
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.