Interest in data mesh and data fabric architectures is surging again after being overshadowed by AI, according to a new analysis from DBTA. The revival stems from AI systems' hunger for seamless information flow, which has pushed organizations to reconsider the flexibility these approaches offer. Rather than treating mesh and fabric as competing philosophies, companies are now layering them together to balance domain autonomy with centralized governance.
The report finds that enterprises aren't implementing data mesh or data fabric exactly as originally described. Most companies are adopting what insiders call a "meshish" approach—embracing ownership principles and product mindsets while maintaining strong central platform teams instead of fully decentralizing infrastructure. Organizations want domain teams to operate independently and reach data more easily, but they refuse to surrender centralized governance, security, lineage, or quality controls. Fabric is becoming the default starting point for new builds, particularly in cases where data fragmentation limits decision-making speed or blocks high-priority digitalization initiatives like AI. Use cases cluster around reliability, process optimization, digital twins, planning and scheduling, and enterprise reporting.
"Ironically, AI has helped bring data mesh and fabric back," Tom Thomas, senior data engineering manager at Indeed, told DBTA. "As organizations started building AI products and pilots, they found that AI is only as good as the data behind it." The report notes that for years the industry treated mesh and fabric as competing philosophies, as if you had to pick a side—but that's no longer the conversation. According to the analysis, mesh now defines the ownership model while fabric provides the plumbing that makes that ownership model technically workable. Demand is real, but execution is falling behind: most organizations are building data architectures, yet far fewer have the operational maturity to make those products reliable, reusable, or measurable.
The report identifies AI as one of the biggest drivers behind the re-emergence of mesh and fabric as a key initiative. Large language models and AI agents need data that's trustworthy, semantically understood, and governed—and most enterprises simply don't have that today. That single requirement is doing more to push fabric adoption than a decade of data warehouse modernization arguments ever did. The greatest AI challenge for enterprises isn't choosing a model or securing more compute capacity; the real bottleneck is their data. If data isn't easy to find, trusted by users, or managed consistently, even the most advanced AI projects struggle to deliver value. When agents need to query across domains in real time, problems with ownership, freshness, and access control stop being architectural concerns and start being operational fires.
The emerging trend to watch is how data mesh and model context protocol are converging and their impact on the efficacy of AI agents, the report concludes. Domain data products become directly consumable by AI agents with governance actually baked in, not bolted on. A mesh or fabric achieves the long-sought goal of a unified view of an organization's data without piling all the overhead onto the IT team, pushing decision making closer to the people who understand and live that data every day rather than routing everything through a centralized IT function that may not grasp the intricacies. Organizations that proceed without that convergence in mind will find themselves redesigning sooner than planned. The choice between decentralized empowerment and centralized control has always created tension in enterprise technology, but this time the stakes involve whether entire AI initiatives succeed or stall before reaching production.