DataTerminology.comNEW
Also known as: Degraded Data Lake, Data Lake Anti-pattern
A poorly governed data lake that becomes hard to find, trust, or use due to missing metadata and controls.
DESCRIPTION
A data swamp is a deteriorated data lake where unmanaged growth, missing metadata, and weak governance render data inaccessible or untrustworthy. Without stewardship, cataloging, and quality controls, schema-on-read storage devolves into opaque, costly sprawl. Remediation involves catalogs, lineage, access policies, lifecycle management, and curating high-value datasets—often via lakehouse patterns. Preventative governance and design are far cheaper than recovery.
ALTERNATIVE DEFINITIONS
Wikipedia
Without proper governance and metadata, a data lake can quickly become a data swamp.
Warns that governance lapses turn lakes into swamps.
Gartner
Without established governance and metadata management, data lakes are prone to becoming data swamps—repositories that are hard to navigate and provide little value.
Emphasizes value erosion and navigability issues.
Databricks
A data swamp is a poorly managed data lake that is either inaccessible or no longer provides value to the business.
Highlights business value loss and accessibility problems.
RELATED TERMS
Data Lake Metadata Management Data Discovery Platform Governance Data Quality Schema-less Lineage Access Control Data Stewardship
COMPETING TERMS
Data Lakehouse Managed Data Lake
KNOWLEDGE AREAS
Data Management Data Architecture Data Quality Metadata Management Data Governance
TARGET AUDIENCE
Chief Data Officer Data Architect Data Steward Data Governance Manager Data Engineer Data Management Consultant
EXTERNAL SOURCES
- Wikipedia - Data lake
- Databricks - Vendor glossary and remediation advice
- AWS - Best practices to avoid swamps
- Microsoft - Architecture guidance for data lakes
TOP QUESTIONS
Why do Data Swamps occur?
Rapid ingestion without metadata, stewardship, or lifecycle controls causes sprawl, making data hard to find or trust.
Category: Relevancy
How can organizations prevent a Data Swamp?
Implement catalogs, lineage, access policies, and quality checks, and define ownership and lifecycle management before mass ingestion.
Category: Guidance
What are signs of a Data Swamp?
Unknown data owners, missing documentation, redundant datasets, and widespread distrust in lake data are telltale symptoms.
Category: Testing
What is the risk of a Data Swamp?
Operational costs rise while value collapses. Analytics slow, and compliance risks grow due to unknown or sensitive data.
Category: Risks
How does a Lakehouse address Data Swamps?
Lakehouses add schema, ACID tables, governance, and performance layers, curbing sprawl and improving reliability.
Category: Alternatives
Where to start remediating a Data Swamp?
Inventory and catalog high-value domains, apply quality and retention policies, and deprecate toxic or redundant datasets.
Category: How-to
What tools help avoid Data Swamps?
Data catalogs, lineage platforms, data quality monitors, and policy engines provide visibility and control.
Category: Platform
What’s a common misunderstanding about Data Swamps?
Believing more data always adds value; without governance, more data often increases noise and cost.
Category: Misunderstanding
Who is accountable for preventing Data Swamps?
Data owners, stewards, and governance leaders must enforce standards; engineers implement controls as part of platform design.
Category: Management