A graph is not a set of nodes. Getting to the root of GraphQL complaints.

The text discusses the misconception that treating graphs like sets of nodes diminishes the value of GraphQL. It highlights how common GraphQL federation often overlooks building relations between aggregated endpoints, leading to the impression that constructing a GraphQL API is redundant work. However, it argues that this approach undervalues GraphQL's true potential. The text then introduces Hasura as an alternative solution that focuses on models, types, and relations to define a supergraph. It explains how declaratively defining data sources and their connections enables Hasura to automatically build an execution engine that leverages these relationships for efficient querying. The author emphasizes the benefits of using a model-based approach to constructing supergraphs, as seen in companies like Meta, Netflix, Goldman Sachs, and Airbnb. The text further explains how the supergraph abstraction can unify various data sources by mapping concepts of models (nodes) and relationships (edges) to different types of databases. It also highlights how Hasura's consistent query interface across diverse data stores allows developers to focus on semantics and structure without worrying about underlying implementations. In conclusion, the text suggests that GraphQL truly shines when used as a query language for rich supergraphs built with tools like Hasura. The supergraph is versatile enough to service any protocol, making it an ideal solution for constructing high-performance, domain-driven GraphQL APIs.