Source: thenewstack.io
The Case for a Federated Data Access Layer with GraphQL
The problem of data being siloed across multiple systems, yet applications wanting one view of the data, has been a universal one for decades. Traditionally, there are three parts to effectively achieving one view of the data: A metadata view of enterprise data sources.
A uniform approach to accessing all the data sources, leveraging the metadata.
Federated Data Access https://www.linkedin.com/in/anantjhingran Gartner and others are beginning to describe these parts and the best practices surrounding them as data meshes or data fabrics.
Perhaps, most importantly, good GraphQL servers balance the three parts needed to effectively achieve one view of the data — metadata, query and runtime — in an iterative manner.
A uniform approach to accessing all the data sources, leveraging the metadata.
Federated Data Access https://www.linkedin.com/in/anantjhingran Gartner and others are beginning to describe these parts and the best practices surrounding them as data meshes or data fabrics.
Perhaps, most importantly, good GraphQL servers balance the three parts needed to effectively achieve one view of the data — metadata, query and runtime — in an iterative manner.
Related Articles
Community Partners
DevOps Careers