Jump to content

Database caching

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Trixie05 (talk | contribs) at 10:59, 31 August 2013 (→Benefits). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Many applications today are being developed and deployed on multi-tier environments that involve browser-based clients, web application servers and backend databases[1][2]. These applications need to generate web pages on-demand by talking to backend databases because of their dynamic nature, making middle-tier database caching an effective approach to achieve high scalability and performance[3].

In three tier architecture, application tier and data tier will be in different hosts. Throughput of the application is affected by the network speed. This network overhead shall be avoided by having database at the application tier. As commercial databases are heavy weight, it is not practically feasible to have application and database at the same host. There are lot of light-weight databases available in the market, which shall be used to cache the data from the commercial databases.

Benefits

  • Scalability: distribute query workload from backend to multiple cheap front-end systems.
  • Flexibility: achieve QoS, where each cache hosts different parts of the backend data, e.g., the data of Platinum customers are cached while that of ordinary customers are not.
  • Availability: by continued service for applications that depend only on cached tables even if the backend server is unavailable.
  • Performance: by potentially responding fast because of locality of data and smoothing out load peaks by avoiding round-trips between middle-tier and data-tier[4]

Potential design elements

Updateable Cache Tables
Most of the existing cache solutions are read-only which limits their usage to small segment of the applications, non-real time applications.
Bi-Directional updates
For updateable caches, updates, which happen in cache, should be propagated to the target database and any updates that happen directly on the target database should come to cache automatically.
Synchronous and asynchronous update propagation
The updates on cache table shall be propagated to target database in two modes. Synchronous mode makes sure that after the database operation completes the updates are applied at the target database as well. In case of Asynchronous mode the updates are delayed to the target database.

Synchronous mode gives high cache consistency and is suited for real time applications. Asynchronous mode gives high throughput and is suited for near real time applications.

Multiple cache granularity: Database level, Table level and Result-set caching
Major portions of corporate databases are historical and infrequently accessed. But, there is some information that should be instantly accessible like premium customer’s data, etc.
Recovery for cached tables
In case of system or power failure, during the restart of caching platform all the committed transactions on the cached tables should be recovered.
Tools to validate the coherence of cache
In case of asynchronous mode of update propagation, cache at different cache nodes and target database may diverge. This needs to be resolved manually and the caching solution should provide tools to identify the mismatches and take corrective measures if required.
Horizontally Scalable
Clustering is employed in many solutions to increase the availability and to achieve load balancing. Caching platform should work in a clustered environment spanning to multiple nodes thereby keeping the cached data coherent across nodes.
Transparent access to non-cached tables reside in target database
Database Cache should keep track of queries and should be able to intelligently route to the database cache or to the origin database based on the data locality without any application code modification.
Transparent Fail over
There should not be any service outages in case of caching platform failure. Client connections should be routed to the target database.
No or very few changes to application for the caching solution
Support for standard interfaces JDBC, ODBC etc. that will make the application to work seamlessly without any application code changes. It should route all stored procedure calls to target database so that they don’t need to be migrated.

Products

  • CSQL Cache - To cache tables from MySQL, Postgres and Oracle.
  • memcached- To cache result set of queries
  • AppFabric Caching- To cache result set of queries
  • Windows Azure Caching- To cache result set of queries in Windows Azure
  • TimesTen - To cache ORACLE tables
  • SafePeak - Automated caching of result sets of queries and procedures from SQL Server, with automated cache eviction for full data correctness

References

  1. ^ MTCache: Transparent mid-tier database caching (2004)
  2. ^ Dbcache: Database caching for web application servers (2002)
  3. ^ Dbcache: Database caching for web application servers (2002)
  4. ^ "Middle-tier Database Caching for e-Business".
Retrieved from "https://en.wikipedia.org/enwiki/w/index.php?title=Database_caching&oldid=570930569"