After initial cache loading, incremental caching improves caching performance by only updating the cache, rather than reloading it, to reflect changes in the data source. Resources are incrementally maintained as highly available and responsive caches that are kept in sync with real-time data in the data source. TDV’s incrementally maintained caches provide the authenticated and authorized end-user client with synchronized data services ready with data results on demand. The following two options are available:

Pull-based incremental caching can be set up using the TDV caching mechanism with two scripts. With pull-based incremental caching the user or client application must make a request for their copy of the cache to be synchronized with the centralized cache copy. For more information on pull-based incremental caching, see Setting Up Pull-Based Incremental Cache.

Push-based incremental caching can be set up using the native TDV caching mechanism, plus the TDV Cache Management Service (CMS), to configure a Central Event Server. If you have subscribed to notices from objects that store data in an incremental cache, subscribed clients are notified whenever the result sets are updated. For more information on push-based incremental caching, see Setting Up Push-Based Incremental Caching for Oracle.