From eee21ad6fd868a704a02de67a4af4d65df11b5a5 Mon Sep 17 00:00:00 2001 From: Sears Russell Date: Sat, 22 Apr 2006 20:17:35 +0000 Subject: [PATCH] more tweaks --- doc/paper3/LLADD.tex | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/doc/paper3/LLADD.tex b/doc/paper3/LLADD.tex index ba17424..d422993 100644 --- a/doc/paper3/LLADD.tex +++ b/doc/paper3/LLADD.tex @@ -132,16 +132,32 @@ simultaneously. Modern systems that deviate from this description are often forced to use existing systems in degenerate ways, or to reimplement complex, bug-prone data manipulation routines by hand. +%Examples include: +%\begin{itemize} +%\item Search engines +%\item Document repositories (including desktop search) +%\item Web based email services +%\item Web based map and gis services +%\item Ticket reservation systems +%\item Photo, audio and video repositories +%\item Bioinformatics +%\item Version control systems +%\item Workflow applications +%\item CAD/VLSI applications +%\item Directory services +%\end{itemize} + Examples of real world systems that currently fall into this category are web search engines, document repositories, large-scale web-email services, map and trip planning services, ticket reservation systems, photo and video repositories, bioinformatics, version control systems, workflow applications, CAD/VLSI applications and directory services. + Applications that have only recently begun to make use of high-level database features include XML based systems, object persistance mechanisms, and enterprise management systems (notably, SAP R/3). -In short, we beleive that a fundamental architectural shift in +In short, we believe that a fundamental architectural shift in transactional storage is necessary before general purpose storage systems are of practical use to modern applications. Until this change occurs, databases' imposition of unwanted