
We currently worked with an API that had to scale to serve multiple regions and millions of users. Introducing caching for such numbers is a common and battle-tested way to reduce costs. With services like Stellate, this is no longer impossible even when using GraphQL.
That is great news, however, also poses some challenges. We need to pay attention to how structure our types so we can fully utilize caching.
How to rethink some GraphQL schema designs so we can have the best of the data-driven paradigm of GQL and have amazing caching capabilities at the same time?


Welcome to the London GraphQL community! Meet quarterly with fellow developers and companies in the GraphQL space and stay up to date with the latest developments, trends and lessons from the GraphQL community!
Interested in speaking? Apply here: http://tinyurl.com/londongraphqlcfp
When caching is done correctly, you never go down, save significant infrastructure costs, and have globally unbeatable performance. However, caching is known as one of the two hardest problems in computer science for a reason. It turns out that GraphQL and Federation make caching a breeze. Max, the CEO at Stellate, shares what they have learned from caching hundreds of federated GraphQL APIs at scale that you can apply to your API to make them indestructible.
Platform Sponsors

Don't let broken lines of code, busted API calls, and crashes ruin your app. Join the 4M developers and 90K organizations who consider Sentry “not bad” when it comes to application monitoring. Use code “guild” for 3 free months of the team plan.
https://sentry.io

Torc is a community-first platform bringing together remote-first software engineer and developer opportunities from across the globe. Join a network that’s all about connection, collaboration, and finding your next big move — together.
Join our community today!

We currently worked with an API that had to scale to serve multiple regions and millions of users. Introducing caching for such numbers is a common and battle-tested way to reduce costs. With services like Stellate, this is no longer impossible even when using GraphQL.
That is great news, however, also poses some challenges. We need to pay attention to how structure our types so we can fully utilize caching.
How to rethink some GraphQL schema designs so we can have the best of the data-driven paradigm of GQL and have amazing caching capabilities at the same time?


Welcome to the London GraphQL community! Meet quarterly with fellow developers and companies in the GraphQL space and stay up to date with the latest developments, trends and lessons from the GraphQL community!
Interested in speaking? Apply here: http://tinyurl.com/londongraphqlcfp
When caching is done correctly, you never go down, save significant infrastructure costs, and have globally unbeatable performance. However, caching is known as one of the two hardest problems in computer science for a reason. It turns out that GraphQL and Federation make caching a breeze. Max, the CEO at Stellate, shares what they have learned from caching hundreds of federated GraphQL APIs at scale that you can apply to your API to make them indestructible.
Platform Sponsors

Don't let broken lines of code, busted API calls, and crashes ruin your app. Join the 4M developers and 90K organizations who consider Sentry “not bad” when it comes to application monitoring. Use code “guild” for 3 free months of the team plan.
https://sentry.io

Torc is a community-first platform bringing together remote-first software engineer and developer opportunities from across the globe. Join a network that’s all about connection, collaboration, and finding your next big move — together.
Join our community today!
Get in touch!
hi@guild.host