Are you planning to use GraphQL and have questions about how you can use it, will it scale as you continue to grow, what all hurdles you can face and what all benefits you can get if you adapt it, then do hear out our story on how we leveraged GraphQL on an API Gateway. Since the inception of the GraphQL at Tokopedia, we have been working on creating a resilient process to govern the GraphQL ecosystem. We'll see how our GraphQL system evolved as we continued to grow to 400K RPS at the peak, to having more than 150+ services/modules integrated. How GraphQL modules can help setup clearly defined ownership and have seperation of concerns and thereby making our system more resilient, maintainable and observable. Just having GraphQL does not ensure its usability, we had to make the integration process more engaging, seamless and pain-free for our engineers. We will be showing how we have developed automation and tooling around our GraphQL ecosystem to achieve this. We'll also be discussing caching in our GraphQL ecosystem. In the end, I'll be talking about a few GraphQL features which we are exploring for our use case and soon to be used in our production system (Subscription and Federation)

Are you planning to use GraphQL and have questions about how you can use it, will it scale as you continue to grow, what all hurdles you can face and what all benefits you can get if you adapt it, then do hear out the talk on how we leveraged GraphQL on an API Gateway.