As API performance is critical to ensuring an enhanced experience for your audience, at the end of 2022, we started working on a new approach to edge caching and introduced our new high-performance endpoint for the content API.
Over the past few months, we have introduced significant improvements to the new endpoint, which included model-and-stage based partial cache invalidations.
We have now launched another major improvement to the new endpoint; our popular and unique GraphQL Mutations, which was previously only available on the regular endpoint.
The launch of GraphQL Mutations for the new high-performance endpoint, along with partial cache invalidations makes it our most advanced endpoint yet. We've also received great feedback about the new endpoint from the community and have planned several improvements to it for the future iterations.
Therefore, we have decided to replace the old endpoint with the new and improved high-performance endpoint by the end of this year.
To switch to the new endpoint, go to project settings > API Access. Copy the URL under the high-performance content API, and replace it with the existing endpoint in your frontend application.
In this article, we will further explain how the new endpoint is better than the previous one.
#How is the new endpoint better?
It's faster
The new endpoint provides low latency and high read-throughput. Hence, applications load faster for your end-users, which leads to improved engagement and user satisfaction.
Offers model-and-stage-based partial cache invalidations
The new endpoint offers model-and-stage-based partial cache invalidations. Further granular partial cache invalidations will be released later this year.
Since the entire cache is not invalidated, content is more often served from the cache than the origin, which leads to a higher cache hit ratio. As a result, downstream applications load much faster.
All of this is offered without any code changes on your end.
Supports both read-and-write operations
The new endpoint now supports our powerful GraphQL Mutations.
#Timelines
The old endpoint will no longer be accessible on new projects.
We will deprecate the old endpoint on existing projects by the end of this year. Please make sure to replace the old endpoint with the new one wherever it is used.
Feel free to share your thoughts on our community channel or reach out to us for assistance if needed.
Blog Author