Chapter 12. Microsoft Fabric API for GraphQL
If you have a developer background or role, you may be wondering, We are creating a custom dashboard using code, and we need the data stored inside Microsoft Fabric—can we access it in some way other than via a SQL analytics endpoint?
This is a real-life requirement we’ve encountered multiple times. And the short answer is, yes, you can! For the longer answer, we encourage you to read this chapter and understand how to leverage the Fabric API for GraphQL feature for an enhanced data retrieval experience compared to the traditional REST API approach.
Honestly, the official name, Fabric API for GraphQL, sounds too scary even for experienced data professionals, let alone someone who just started their Fabric learning journey, unless you are a seasoned application developer. Hence, let’s first try to demystify the core concepts of this feature.
First and foremost, GraphQL is a query language. You might have already assumed that from its name (QL stands for query language). To take this one step further: it’s not any query language—it’s a query language for the API. It’s an open source protocol and has been successfully implemented in numerous programming languages. Since GraphQL is an API query language, it isn’t bound to any particular database engine or vendor.
From a high-level perspective, the main advantages of GraphQL compared to REST APIs are:
- Flexibility
-
GraphQL allows you to define individual columns that you need to extract, ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access