TY - GEN
T1 - Middle-tier database caching for e-business
AU - Luo, Qiong
AU - Krishnamurthy, Sailesh
AU - Mohan, C.
AU - Pirahesh, Hamid
AU - Woo, Honguk
AU - Lindsay, Bruce G.
AU - Naughton, Jeffrey F.
N1 - Publisher Copyright:
© 2002 ACM.
PY - 2002/6/3
Y1 - 2002/6/3
N2 - While scaling up to the enormous and growing Internet population with unpredictable usage patterns, E-commerce applications face severe challenges in cost and manageability, especially for database servers that are deployed as those applications' backends in a multi-tier configuration. Middle-tier database caching is one solution to this problem. In this paper, we present a simple extension to the existing federated features in DB2 UDB, which enables a regular DB2 instance to become a DBCache without any application modification. On deployment of a DBCache at an application server, arbitrary SQL statements generated from the unchanged application that are intended for a backend database server, can be answered: at the cache, at the backend database server, or at both locations in a distributed manner. The factors that determine the distribution of workload include the SQL statement type, the cache content, the application requirement on data freshness, and cost-based optimization at the cache. We have developed a research prototype of DBCache, and conducted an extensive set of experiments with an E-Commerce benchmark to show the benefits of this approach and illustrate tradeoffs in caching considerations.
AB - While scaling up to the enormous and growing Internet population with unpredictable usage patterns, E-commerce applications face severe challenges in cost and manageability, especially for database servers that are deployed as those applications' backends in a multi-tier configuration. Middle-tier database caching is one solution to this problem. In this paper, we present a simple extension to the existing federated features in DB2 UDB, which enables a regular DB2 instance to become a DBCache without any application modification. On deployment of a DBCache at an application server, arbitrary SQL statements generated from the unchanged application that are intended for a backend database server, can be answered: at the cache, at the backend database server, or at both locations in a distributed manner. The factors that determine the distribution of workload include the SQL statement type, the cache content, the application requirement on data freshness, and cost-based optimization at the cache. We have developed a research prototype of DBCache, and conducted an extensive set of experiments with an E-Commerce benchmark to show the benefits of this approach and illustrate tradeoffs in caching considerations.
UR - https://www.scopus.com/pages/publications/85134316515
U2 - 10.1145/564691.564763
DO - 10.1145/564691.564763
M3 - Conference contribution
AN - SCOPUS:85134316515
T3 - Proceedings of the 2002 ACM SIGMOD International Conference on Management of Data, SIGMOD 2002
SP - 600
EP - 611
BT - Proceedings of the 2002 ACM SIGMOD International Conference on Management of Data, SIGMOD 2002
PB - Association for Computing Machinery, Inc
T2 - 2002 ACM SIGMOD International Conference on Management of Data, SIGMOD 2002
Y2 - 3 June 2002 through 6 June 2002
ER -