Workflow and tooling for GraphQL
As a per-data graph way of thinking in GraphQL, data is exposed using an API consisting of graphs of objects. These objects are connected using relations. GraphQL only exposes a single API endpoint. Clients query this endpoint that uses a single data graph. On top of that, the data graph may resolve data from a single source, or multiple sources, by following the OneGraph principle of GraphQL. These sources can be a database, legacy system, or services that expose data using REST/gRPC/SOAP.
The GraphQL server can be implemented in the following two ways:
- Standalone GraphQL service: A standalone GraphQL service contains a single data graph. It could be a monolithic app or microservice architecture that fetches the data from single or multiple sources (having no GraphQL API).
- Federated GraphQL services: It's very easy to query a single data graph for comprehensive data fetching. However, enterprise applications are made using multiple...