2x faster GraphQL edge caching with Fastly
When we first built Stellate, no edge computing platform supported all the necessary primitives to build GraphQL edge caching. So, we combined Fastly and Cloudflare to make it work for you.
In 2023, this is no longer the case. As of last week, all new Stellate services run entirely on Fastly, improving performance by up to 2x! 🚀
Existing services will be automatically migrated on November 1st. If your origin has an IP address-based allowlist (whitelist), you must update it before Nov 1st. See below for more information.
How we improved performance by 2x
Previously, when we forwarded requests to the origin GraphQL API, they would be sent from Fastly to Cloudflare and then to the origin:
We have now migrated entirely to Fastly, which means requests to the origin are sent directly from Fastly to the origin. The extra network hop to Cloudflare is a thing of the past, which is where the significant performance improvement comes from:
What do existing services have to do to migrate?
For anyone without an IP address-based allowlist (i.e. most users), the new infrastructure requires no changes on your end. You can either wait for the automatic migration on November 1st or, if you already want to get the performance benefits, enable the new Fastly-only infrastructure from your service’s settings:
If your origin has an IP address-based allowlist/whitelist, that allowlist contains Cloudflare’s IP addresses. After November 1st, requests to your origin will come from Fastly’s infrastructure instead, so you must update your allowlist to include the new IP addresses. You can read more about how to do this in our documentation.
If you have questions before or after the migration, you can find more information in our documentation or contact our support team.