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 mesh decentralises data ownership, assigning it to business domains.
- It treats data as a product, with its own owners and quality.
- It solves bottlenecks in large organisations with many domains.
- It is not suitable for small companies or small data teams.
- It is organisational, not just technological.
As organisations grow, the model of a single central data team serving the whole company starts to saturate. Data mesh is an architectural and organisational response, though not the universal solution it is sometimes sold as.
What it is
Data mesh decentralises responsibility for data, assigning it to each business domain’s team (sales, logistics, finance), which treats its data as a "product" with its own quality, documentation and owners.
The four principles
- Domain ownership: each area is responsible for its data.
- Data as a product: with quality, documentation and internal "customers".
- Self-service platform: common infrastructure enabling domains.
- Federated governance: common rules applied in a distributed way.
Central team
Bottleneck
Data mesh
Ownership bydomain
Data as product
QualityOwners
What problem it solves
Data mesh tackles the central-team bottleneck: when every data request goes through one team, lead times explode. Distributing responsibility to those who know each domain best improves quality and speed in large, complex organisations.
When NOT to adopt it
Data mesh is not for everyone. It requires organisational maturity, data teams in each domain and a robust self-service platform. For small or mid-sized companies, it adds complexity without solving a bottleneck that may not exist. A centralised, managed data layer is often more effective.
Data mesh solves a bottleneck large organisations have — and small ones often do not.
In summary
Data mesh decentralises data ownership to business domains, treating data as a product under federated governance. It relieves the central-team bottleneck in large, complex organisations — but for small or mid-sized firms it adds complexity without a problem to solve, where a centralised managed layer fits better.
Sources & further reading
Frequently asked questions
Does data mesh replace the data lake or warehouse?
No. It is an organisational and architectural approach to distributing data responsibility; it can rest on lakes, warehouses or lakehouses.
Should every company adopt it?
No. It adds value in large organisations with many domains and data teams. In small or mid-sized companies it usually adds unnecessary complexity.
What does "data as a product" mean?
Treating each dataset as seriously as a product: with an owner, guaranteed quality, documentation and internal users it serves.
What problem does data mesh solve?
The central-team bottleneck: when every request goes through one team, lead times explode. It distributes responsibility to domain teams.
What are its four principles?
Domain ownership, data as a product, a self-service platform and federated governance.
When should I not adopt it?
When you lack organisational maturity, domain data teams or a robust self-service platform — a centralised managed layer is then more effective.
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.