When you treat your graph like a set of nodes, you miss the point of GraphQL.
...leads to the common impression that building out a GraphQL API is busy work... And moreover, this is true! This way of doing things sells GraphQL short.
...serious GraphQL users like Meta and Netflix have their own entity based frameworks to construct supergraphs.
Building an app or API without a supergraph is like storing your data in files instead of a relational database.
...leads to the common impression that building out a GraphQL API is busy work... And moreover, this is true! This way of doing things sells GraphQL short.
...serious GraphQL users like Meta and Netflix have their own entity based frameworks to construct supergraphs.
Building an app or API without a supergraph is like storing your data in files instead of a relational database.