Is your organization ready for a data mesh? For decades, the standard approach to data platforms and architecture has assumed centralisation: a common platform with bound technologies handled by a centralised team. With this guide, find new insights, perspectives, and directions to help you get started on your Data Mesh journey.
Despite the progress made with this approach, it’s often plagued by issues appearing with increasing team size and technical complexity. These can appear in multiple ways such as the increasing distance between the data experts and the business domains, a cumbersome platform that’s slow to bend for different needs or a team being out of step with current business goals.
Data mesh is an up-and-coming paradigm that outlines an organisational approach to data and how to create the technical as well as cultural requirements that help organisations to address many of the pain points associated with prevailing data platform approaches. First introduced by Zhamak Dehghani, data mesh takes an approach derived from domain-driven design and introduces it into the data world. There’s a lot more to it than just technical change – data mesh is first and foremost a way of thinking and organising, which adopts modern product development practices and a decentralised approach to data architecture.
In this piece we’ll cover:
• When organisations should consider data mesh
• The role of technology in data mesh architecture
• How to build the right teams and culture to support data mesh
In our Data Mesh guide you'll find new insights, perspectives, and steps to take that will help you choose the right direction for your Data Mesh journey.