What is a data mesh?
A data mesh is a way of organizing data work in which responsibility for analytical data is distributed to the business domains that produce it, rather than concentrated in one central team. Each domain treats its data as a product with an owner, a service level, documentation, and a data contract that consumers can rely on. A central platform team provides the shared infrastructure, the catalog, and the governance rules every product must follow, so domains build on common tools without waiting in a central queue.
Why a data mesh matters
Central data teams become bottlenecks as a company grows, and they rarely understand the data as well as the people who create it. A mesh moves the modeling decisions to those people. A national staffing firm with healthcare, industrial, and office divisions used a mesh so each division published its own placement and billing data, while the shared platform enforced one definition of a billable hour. The cost is coordination, and the mesh only works if the domains have the skills and the standards hold.
What to watch for
- Check that each domain has, or will hire, someone able to own a data product, because the model fails without that person.
- Agree on cross-domain identifiers such as customer and employee before publishing, or the products will not join.
- Compare the mesh, which is an operating model, with the data fabric, which is a technology approach to the same problem.