Sybase Data Federation uses caching to insulate production data sources from haphazard access, to maintain good performance for users and applications, to refresh data in a granular way based on business needs, and to ensure maximum data availability.
Local caching enables caching of frequently requested results near the data source to reduce load on the back-end data source.
Remote caching (which is remote from the data source) caches data close to the users or applications that will use it. This cuts down on network congestion and dramatically improves application performance, because remote data calls are eliminated. You can prepopulate and update caches during off hours when network load is low, and establish cache configurations that ensure high availability when a network is congested or unavailable.
You can specify cache update frequency for a given data item. Database administrators can schedule how often database operations should be re-run and cached, so as to protect production databases from unexpected load. You can also set cached data to expire after a set time period, which forces a refresh of the data on the next request.
An automated caching approach means fewer data stores to manage. Caches are updated automatically in accordance with your specifications, and the process is completely transparent to users and applications.
For more information on caching in Data Federation, see the Data Federation Provisioning and Advanced Data Integration Guide, part of the DI Suite documentation set, which is available on the Sybase Product Manuals Web site at http://sybooks.sybase.com.
For product-related issues, contact Sybase Technical Support at 1-800-8SYBASE. Send your feedback on this help topic directly to Sybase Technical Publications: pubs@sybase.com