data warehouse as a walled garden

Discipline

Databases

Form

Database Analogies

Attribution — Origin / Source

Collected by Daphne Miedema — Hellerstein, J. M., & Stonebraker, M. (2005). Readings in Database Systems. 4 ed. MIT Press.

Topic

Conceptual modeling

Domain

Anything else

Conceptual Advantage

Evokes a visual of how clean and curated the data is

Mapping

SymbolConcept
traditional data warehouse systems walled gardens - ingested data is pristine, curated, and has structure.
MapReduce systems process arbitrarily structured data, whether clean or dirty, curated or not. There is no loading step. This means users can store data first and consider what to do with it later.

Draws Attention To

Highlights how clean data is important for traditional systems, but not for MapReduce systems.

Details

Text

traditional data warehouse systems are walled gardens: ingested data is pristine, curated, and has structure. In contrast, MapReduce systems process arbitrarily structured data, whether clean or dirty, curated or not. There is no loading step. This means users can store data first and consider what to do with it later.

Comments or Feedback?

Do you have feedback on this notional machine? Did you find a mistake, or do you have a request for improvement? You can create an Issue on GitHub, where the description is hosted. This way we can see your feedback and address it.

For this, you need a GitHub account. Then follow this link to see the source file of this page. In there, click the ... left of the highlighted line, then pick "Reference in a new issue".

Create an Issue on GitHub