Jump to content

Database caching

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Dsetrakyan (talk | contribs) at 00:05, 14 April 2017 (→Products). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Database caching is a process included in the design of computer applications which generate web pages on-demand (dynamically) by accessing backend databases.

When these applications today are deployed on multi-tier environments that involve browser-based clients, web application servers and backend databases,[1][2] middle-tier database caching is used to achieve high scalability and performance.[2]

In a three tier architecture, the application tier and data tier can be in different hosts. Throughput of an application can be limited by the network speed. This limitation can be minimized by having the database at the application tier. Because commercial database software makes extensive use of system resources, it is not always practical to have the application and the database at the same host. In this case, a more light-weight database application can be used to cache data from the commercial database.

Benefits

Database caching improves scalability by distributing query workload from backend to multiple cheap front-end systems. It allows flexibility in the processing of data; for example, the data of Platinum customers can be cached while that of ordinary customers are not. Caching can improve availability of data, by providing continued service for applications that depend only on cached tables even if the backend server is unavailable. Another benefit is improved data access speeds brought about by locality of data and smoothing out load peaks by avoiding round-trips between middle-tier and data-tier[3]

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

  • Redis - Distributed in-memory database system, which also supports various distributed caching scenarios
  • CSQL Cache - To cache tables from MySQL, Postgres and Oracle.
  • memcached- 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
  • Apache Ignite
  • GridGain Systems

References

  1. ^ Larson, Per-åke; Goldstein, Jonathan (2004). "MTCache: Transparent mid-tier database caching". CiteSeerX 10.1.1.95.875. {{cite journal}}: Cite journal requires |journal= (help)
  2. ^ a b Altinel, Mehmet; Luo, Qiong; Krishnamurthy, Sailesh; Mohan, C.; Pirahesh, Hamid; Lindsay, Bruce G.; Woo, Honguk; Brown, Larry (2002). "DBCache: Database Caching For Web Application Servers" (PDF). CiteSeerX 10.1.1.104.8991. {{cite journal}}: Cite journal requires |journal= (help)
  3. ^ "Middle-tier Database Caching for e-Business". CiteSeerX 10.1.1.140.8455. {{cite journal}}: Cite journal requires |journal= (help)
Retrieved from "https://en.wikipedia.org/enwiki/w/index.php?title=Database_caching&oldid=775301107"