Update caching docs #1818
Update caching docs #1818
Conversation
|
@mandiwise is attempting to deploy a commit to the The GraphQL Foundation Team on Vercel. A member of the Team first needs to authorize it. |
There was a problem hiding this comment.
let's keep a dedicated caching page on that page we can talk about different caching techniques used within community: Document Caching, Response Caching, Partial Query Caching.
We can talk about performance and add more things to that page. The performace page can link to the caching page. Performance is a broader topic, we can even take things like Trusted documents and refer in performance section.
|
|
||
| Monitoring a GraphQL API over time can provide insight into how certain operations impact API performance and help you determine what adjustments to make to maintain its health. For example, you may find that certain fields take a long time to resolve due to under-optimized requests to a backing data source, or you may find that other fields routinely raise errors during execution. | ||
|
|
||
| Observability tooling can provide insight into where bottlenecks exist in the execution of certain GraphQL operations by allowing you to instrument the API service to collect metrics, traces, and logs during requests. For example, [OpenTelemetry](https://opentelemetry.io/) provides a suite of vendor-agnostic tools that can be used in many different languages to support instrumentation of GraphQL APIs. |
There was a problem hiding this comment.
Let's use this opportunity to add a section to https://graphql.org/community/tools-and-libraries/ around observability and link here to that section so people can go and see specific solutions around that
| ``` | ||
|
|
||
| This is known as the N+1 problem, where the first request to an underlying data source leads to N subsequent requests to resolve the data for all of the requested fields. | ||
|
|
There was a problem hiding this comment.
Can we add here also a mention of solutions that use the selection set and automatically translate it to the underlying data source?
Things like @benjie's Graphile that can turn selection sets into SQL queries, some of GraphQL Mesh's providers that can translate selection sets to oData queries for example
Mostly to explain the concept of query to query
Description
This PR expands on the existing caching content for the Learn docs so that it addresses broader performance topics. Key changes include:
GETto facilitate caching, the N+1 problem, performance monitoring, and more@benjie @jorydotcom