WebView Materialization

Abstract

A <i>WebView</i> is a web page automatically created from base data typically stored in a DBMS. Given the multi-tiered architecture behind database-backed web servers, we have the option of materializing a WebView inside the DBMS, at the web server, or not at all, always computing it on the fly (virtual). Since WebViews must be up to date, materialized WebViews are immediately refreshed with every update on the base data. In this paper we compare the three materialization policies (materialized inside the DBMS, materialized at the web server and virtual) analytically, through a detailed cost model, and quantitatively, through extensive experiments on an implemented system. Our results indicate that materializing at the web server is a more scalable solution and can facilitate an order of magnitude more users than the virtual and materialized inside the DBMS policies, even under high update workloads.

DOI: 10.1145/342009.335430

Extracted Key Phrases

11 Figures and Tables

Unfortunately, ACM prohibits us from displaying non-influential references for this paper.

To see the full reference list, please visit http://dl.acm.org/citation.cfm?id=335430.

Showing 1-10 of 51 extracted citations

Statistics

01020'01'03'05'07'09'11'13'15'17
Citations per Year

127 Citations

Semantic Scholar estimates that this publication has received between 71 and 218 citations based on the available data.

See our FAQ for additional information.