From aa5e9d7b2d0e847e4b372aed84b47ad300139a10 Mon Sep 17 00:00:00 2001 From: Jake Barnby Date: Wed, 12 Oct 2022 22:24:10 +1300 Subject: [PATCH] Update service doc --- docs/services/graphql.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/services/graphql.md b/docs/services/graphql.md index b71b65813b..29a88ba149 100644 --- a/docs/services/graphql.md +++ b/docs/services/graphql.md @@ -1,11 +1,11 @@ -The GraphQL services allows you to manipulate your Appwrite instance through a single endpoint using GraphQL queries and mutations, asking for exactly what you need and nothing more. You can perform any action available in the REST API, as well as directly manipulate your custom collections. +The GraphQL services allows you to manipulate your Appwrite instance through a single endpoint using GraphQL queries and mutations, asking for exactly what you need and nothing more. You can perform any action available in the REST API. > ## GraphQL API vs REST API > > The major difference comes from the way the data is returned. GraphQL returns the data in a structured format, giving you only the nodes you ask for, while REST returns the data in a flat format. > -> GraphQL has a single endpoint for all queries and mutations except file uploads; the REST API has multiple endpoints for each type of action. +> GraphQL has a single endpoint for all queries and mutations except file uploads, while the REST API has multiple endpoints for each type of action. > > Both APIs are fully compatible with each other, and you can use them together in the same project. > -> Both GraphQL and REST have pros and cons. For example, GraphQL requests are very flexible and can be more efficient. However, REST has better support for caching, error handling, and versioning. \ No newline at end of file +> Both GraphQL and REST have pros and cons. For example, while GraphQL requests are very flexible and can be more efficient, REST has better support for caching, error handling, and versioning. \ No newline at end of file