Managed data
What is Data as a Service (DaaS) and why it matters
A clear definition of Data as a Service (DaaS): what it includes, how it differs from building your own infrastructure and why more companies adopt it.
Read articleKey takeaways
- Data lineage traces a data point from its origin to its final use.
- It is key for trust, error debugging and regulatory compliance.
- It enables impact analysis before applying a change.
- It is part of good data governance.
- It must be captured automatically to stay reliable.
When a figure in a report does not add up, the first question is always the same: "where does this number come from?". Answering it in seconds, instead of days, is what data lineage provides. And in an audited environment, reconstructing that path is a requirement, not a convenience.
What it is
Data lineage is the traceability of a data point’s full journey: which source it comes from, what transformations it underwent and in which reports, APIs or models it is used. It is the map of the data’s journey through the organisation.
What it is for
Trust
Prove origin& calculation
Debugging
Locate theerror point
Impact
What breaksif changed
Compliance
GDPRevidence
- Trust: demonstrate the origin and calculation of each figure.
- Debugging: locate exactly where an error was introduced.
- Impact analysis: show what would break if a source or rule changes.
- Compliance: evidence how data is processed, which the GDPR values.
Lineage and compliance
Traceability is not just a technical convenience. EU data protection law requires being able to demonstrate how personal data is processed, and the GDPR’s accountability principle relies on evidence like lineage. In audited environments, reconstructing a data point’s path is a requirement.
Lineage vs. data catalogue
They are complementary: the catalogue describes what data exists and what it means; lineage describes where it comes from and how it transforms. The catalogue tells you what you have; lineage, how it got there.
How it is implemented
Lineage is captured automatically as data flows through pipelines, recording each transformation. Modern platforms document it without manual effort and present it visually. Without automation, keeping lineage current is unfeasible in any evolving architecture.
Lineage turns "where does this number come from?" from a days-long investigation into a seconds-long answer.
In summary
Data lineage traces each data point’s full journey from origin to use, providing trust, debugging, impact analysis and GDPR compliance evidence. It complements the data catalogue and must be captured automatically to stay reliable as the architecture evolves.
Sources & further reading
Frequently asked questions
How does lineage differ from a data catalogue?
The catalogue describes what data exists and what it means; lineage describes where it comes from and how it is transformed. They are complementary.
Why does it matter for compliance?
Because regulations like the GDPR require demonstrating how data is processed. Lineage provides that evidence in a traceable, auditable way.
Does it have to be maintained by hand?
It should not. In modern architectures, lineage is captured automatically as pipelines run, keeping it reliable and up to date.
What is impact analysis?
Knowing which reports, APIs or models would break if a source or rule changes, before applying the change — reducing the risk of surprises.
How does lineage help debugging?
It locates the exact point where a wrong data point was introduced, instead of reviewing the whole process blindly.
Is lineage only for large companies?
It adds value to any organisation that wants to trust its figures and comply with the GDPR; the more complex the architecture, the more essential.
Turn this data into results
Tell us what you want to achieve. Data Layer connects, processes and delivers the result up and running, with no infrastructure for you to manage.