From Data Mesh to Interface Mesh
A Thought Born in London
Yesterday, during a table discussion at the API Economy Summit at apidays London, we landed full-size on the mesh topic. Everyone around the table was talking about Data Mesh. It has become the concept of the moment when it comes to decentralization, federated governance, and product thinking for data. But as the conversation unfolded, a question kept nagging me: why do we talk so much about Data Mesh but almost never about Interface Mesh?
When you look closely, the personas of API producers and consumers already place us in a meshy situation. Producers create interfaces to expose capabilities or data. Consumers depend on them to build value. Every connection adds another link, and what emerges is not a neat hierarchy but a web of dependencies and contracts. This is a mesh in all but name, and yet we treat it as accidental rather than intentional.
Today, I will give my talk “Lost in Translation: Unlocking Integration Success Beyond AsyncAPI”. The core idea there is that focusing only on specifications or standards misses the bigger picture of how integration actually succeeds. In many ways, the Interface Mesh is that bigger picture. AsyncAPI, OpenAPI, or any other specs are useful, but they only work if producers and consumers can find each other, align, and evolve together. Without that, the mesh becomes messy.
This is where APIOps Cycles can make the difference. The method offers a way to turn the implicit mesh into something explicit and governable. The Value Proposition Canvas forces producers to ask what consumers really need. The Interaction Canvas sheds light on the connections between the two sides. These canvases make the mesh visible, create feedback loops, and guide its growth.
If we start to see interfaces as a mesh, we shift from projects to products. Domain teams can own their APIs while federated governance ensures consistency. Consumers become active participants rather than passive recipients. The result is not a tangle of integrations but a mesh that enables agility and scale.
The lively discussions yesterday and the reflections from my talk today converge on one insight: the Interface Mesh is already here. We just need to recognize it and use methods like APIOps Cycles to shape it. Data Mesh and Interface Mesh are two sides of the same coin. Without interfaces, data remains locked. Without data, interfaces are hollow. Only by embracing mesh thinking for both do we unlock the real potential of the API economy.