# Caching an existing Graphql endpoint on kubernetes

**URL:** <https://discuss.konghq.com/t/caching-an-existing-graphql-endpoint-on-kubernetes/11392>\
**Category:** General\
**Tags:** kubernetes, kong-gateway\
**Created:** [April 7, 2023, 2:43pm UTC](https://discuss.konghq.com/t/caching-an-existing-graphql-endpoint-on-kubernetes/11392 "2023-04-07T14:43:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Thomas\_PEDOT](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/thomas_pedot/32/3918_2.png) [@Thomas\_PEDOT](https://discuss.konghq.com/u/Thomas_PEDOT)\
**Post date:** [April 7, 2023, 2:43pm UTC](https://discuss.konghq.com/t/caching-an-existing-graphql-endpoint-on-kubernetes/11392/1 "2023-04-07T14:43:18Z")

</div>

Hello,  
I have a graphql endpoint on top of postgresql database deployed in K8S.

I wonder if it is interesting in terms of performance to deploy Kong gateway connect it to graphql endpoint and use the caching from it ?

What is your experience on it ? Does it make sense ? What is the effort to deploy it for one endpoint ?  
What should I need to look to imagine how much gain I can have ? I have Jaeger tracing in place, I have one span which takes up to 500ms average to be solved.

Thanks for your insights 🙂