Oracle True Cache is a read-only, in-memory, high performance SQL and key-value cache that is automatically managed and consistent. Oracle True Cache improves application response time while reducing the load on the database server. Automatic management and consistency simplify application development—reducing developer effort and cost.
Real-time, consistent data should be the first item followed by simplified cache management. With Oracle True Cache, there’s no change in the order for remaining items.
Improve application performance without rewriting the application, which saves a considerable amount of time, effort, and expenses. Data is always consistent within a single query even when you have joins across multiple rows.
Move to hybrid cloud architectures or support application modernization with a data layer that unifies data across all environments with support for all data types including relational, object, document(JSON/XML), key-value, text, graph, spatial, and data formats.
Oracle True Cache improves scalability and application response time by offloading queries and reducing the number of requests to the database.
Offload workload to low-cost commodity hardware. Automated cache management simplifies application development and improves developer productivity.
True Cache is a fully functional, read-only replica of the database that is mostly diskless. True Cache satisfies queries by using only data from its in-memory buffer cache. If the requested data is not in-memory, True Cache automatically fetches it from the back-end database.
Modern web applications often deploy caches in front of the database to handle a large number of connections and offload database processing. These caches rely on the fact that applications often don't need to see the most current data. For example, when someone browses for flights, the reservation system can show flight data that's one second old. When someone reserves a flight, the system shows the most current data.
Applications can control when to use True Cache versus the back-end database. For example, the application can maintain two connections (a read-only connection to True Cache and a read/write connection to the database). Alternatively, a Java application can use a connection and dynamically switch between True Cache and the database by setting the read-only attribute.
With True Cache, data is always consistent within a single query. This is even more important when there are joins across multiple rows; doing this at the application level can lead to incorrect results.
Oracle True Cache stores ephemeral session data such as user profiles and browsing history, providing microsecond response times and optimizes the performance of real-time recommendation engines.
Customers retrieve data for online product catalogs by accessing the Oracle True Cache instance instead of the back-end database. This process improves response times and elevates the customer experience during peak sales periods such as Black Friday, Cyber Monday, and prime-time television events.
Oracle True Cache reduces latency and improves the immersive gaming experience by storing real-time player data, supporting features such as leader boards and user rankings.
Oracle True Cache handles millions of daily updates to user profiles validating the application user in real time. It also supports multiple data models to natively store different types of elements, reducing complexity and costs.
Oracle True Cache can be used to cache data and offload database I/O to reduce the operational burden, lower costs, and improve the performance of both the database and the application.
Oracle True Cache can be deployed in regions closer to users or devices, reducing the time needed to collect, store, and retrieve data from databases.
Oracle True Cache offloads reads to instances that are deployed closer to the end user or sovereign regions, speeding up analytics response times and maintaining data sovereignty.
Introducing Oracle True Cache : In-memory, consistent, and automatically managed SQL and key-value (object) cache.