Data mesh is a sociotechnical approach to building a decentralized data architecture by leveraging a domain-oriented, self-serve design (in a software development perspective), and borrows Eric Evans’ theory of domain-driven design[1] and Manuel Pais’ and Matthew Skelton’s theory of team topologies.
[6] The term data mesh was first defined by Zhamak Dehghani in 2019[7] while she was working as a principal consultant at the technology company Thoughtworks.
[8][9] Dehghani introduced the term in 2019 and then provided greater detail on its principles and logical architecture throughout 2020.
[16] Data mesh is based on four core principles:[17] In addition to these principles, Dehghani writes that the data products created by each domain team should be discoverable, addressable, trustworthy, possess self-describing semantics and syntax, be interoperable, secure, and governed by global standards and access controls.
Challenges (C) and best practices (BP) for practitioners, include: Scott Hirleman has started a data mesh community that contains over 7,500 people in their Slack channel.