A WebView is a web page automatically created from base data typically stor
ed in a DBMS. Given the multi-tiered architecture behind database-backed we
b 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). S
ince WebViews must be up to date, materialized WebViews are immediately ref
reshed with every update on the base data. In this paper we compare the thr
ee materialization policies (materialized inside the DBMS,; materialized at
the web server and virtual) analytically, through a detailed cost model, a
nd quantitatively, through extensive experiments on an implemented system.
Our results indicate that materializing at the web server is a more scalabl
e solution and can facilitate an order of magnitude more users than the vir
tual and materialized inside the DBMS policies, even under high update work
loads.