Data Mesh

How to Access Game-Changing Architecture to Power a Client-Centric Organization

Dash mesh is often hailed as a game changer in the world of data architecture, yet it is often misunderstood, leading organizations to frustration when it is not designed or implemented within a clear business strategy. In this new white paper, co-written by BCG Platinion and Teradata, we uncover the true purpose and potential of data mesh architecture. We analyze the principles behind this concept and how it can be designed and implemented to achieve client-centric business goals.


Read our white paper in full length!

Dive deeper into the world of data mesh


Although data mesh is a new and revolutionary construct, it is based on sound elements of data organization. Fundamentally, it reorients data architecture and organizes information and interfaces in a client-centric way. By deconstructing entangled and monolithic data and rearranging it in a domain-orientated infrastructure, data mesh enables self-service through decentralization and federation.


By building architecture in this way, data owners have the autonomy to structure, adapt, and use their data in the most effective way. Since data is harmonized through a centralized method, consistent federated governance is maintained and common discovery, consumption, and interoperability are achieved. Although data mesh offers many benefits, there is much misunderstanding about how it can and should be used. In addition, many organizations have questions about how to effectively design and implement this architecture.


In this white paper, we delve deep into the topic of data mesh, uncover common misconceptions, shed light on architectural concepts and effective implementation strategies, and look at the future landscape of data mesh as an empowering business tool.



The fundamental principles of data mesh, including domain orientation, viewing data as a product, self-service rules, and the importance of federated governance

The architectural concepts that support data mesh, including domain-driven design, microservice architecture, API-driven integration, and resource-oriented structures

The differences between data mesh, data warehouses, and data lakes, as well as the importance of good data management

How organizations can organize and source distributed data mesh

The importance of domain-driven design as a foundation for data mesh architecture

The organizational factors that impact data mesh and the importance of viewing this architecture as a business philosophy rather than a technical concept

The limitations of data mesh

The future landscape of data mesh as it powers more contained, multi-disciplinary teams, the removal of siloed operations, and shorter, more precise development cycles

The use of Teradata as a core technology within data mesh architecture

For all of this and much more, download “How to Build, Implement, and Leverage a Successful Data Architecture Using a Data Mesh Architecture Pattern.”


This article was written in collaboration with Teradata and is co-authored by Robbert Naastepad.

Read our white paper in full length!

About the Authors

Jens Müller

IT Architecture Director
Frankfurt, Germany

Jens is an engineer to the core. He started by coding J2EE solutions in financial industries and evolved into a domain/enterprise architect over the years through performance measurement and optimization cases, which helped him to build a thorough understanding of traditional relational DBMS and their inner workings (Oracle and DB2). Moving on to strategic IT consulting in 2006, he explored all aspects of IT management. The path to data platforms was laid out in pilot cases on SAS around 2010 and then, from 2012 on, he took over the role of head of design authority capital markets at a large German bank, where he substantially helped set up a data hub based on data lake and streaming technologies that was later moved to a cloud native setup. After rejoining BCG Platinion in 2019, Jens took over the Data Architecture chapter to extend our competences further and work on (cloud) data platform cases in financial industries.

Jakub Fila

Warsaw, Poland

Jakub has a professional background as an aerospace engineer, first in the turbine engine industry and then in the nuclear industry. He is a graduate of aerospace engineering and physics faculties, where he also learned software engineering and started his interest in data processing and parallel programming. He has been working as an IT architect of various levels of seniority for companies such as Accenture, IBM, or Teradata. Jakub is now a Principal at BCG Platinion, helping clients to make strategic decisions and implement the right technologies to fulfill their strategy. He specializes in integration architecture, enterprise architecture, massive data processing, and software engineering and is an enthusiast in MPP platforms and efficient parallel programming techniques. Jakub leads the Application Architecture chapter at BCG Platinion in the EMESA region. His private interests lie in aerospace and triathlons.

Vincent von Hof

Lead IT Architect
Cologne, Germany

Vincent is a Senior IT Architect at BCG Platinion and an engineer by his background and passion. Vincent is a key member of BCG Platinion’s Data chapter. Vincent started his career as a software developer focused on Java and C#, solving data challenges in the middleware and backend for large-scale data processing and creating data ontologies for the German government, as well as working on solving data challenges on the opposite scale in constrained environments on Android, where he led a development team at a startup for multiple years. He holds PhD in software engineering, majoring in automated test case generation. With over 10 years of development experience, he joined BCG Platinion as an Architect. His main interests include massive data processing, software engineering, test automation, and cloud architecture. Vincent typically leads large data management projects delivering content and architecture concepts, and implementing and aligning business with IT.