We're thrilled to announce the launch of improved support for Next.js Incremental Static Regeneration (ISR) on Atlas.
What improvements does this release include?
In most cases, Next.js Incremental Static Regeneration (ISR) works as expected on Atlas - however, there are two issues:
- Traffic Spikes:When traffic spikes, new replicas of the application are spawned. These replicas mirror the version of the application that was originally built, which includes statically generated content that may now be outdated.
- Low Traffic Periods:Conversely, if a site receives no traffic for an extended period, the application scales down. When traffic picks up again, the initial visitors encounter this outdated content. This content isn’t cached; instead, it initiates a background revalidation process. After this process is complete, any subsequent requests will receive the freshly updated content, which is then cached.
Our solution for ISR support effectively addresses both issues, ensuring your site always displays the most recent content, regardless of traffic patterns. If your sites use Next.js Incremental Static Regeneration, we recommend using
@wpengine/atlas-next
package to ensure your content is going to be up to date regardless of the traffic patterns to your sites.Does that mean Atlas supports on-demand Incremental Static Regeneration now?
Currently, on-demand ISR is not supported on Atlas. However, our team is actively working on adding this feature to our platform. Once it’s available, the use of the
@wpengine/atlas-next
package will be required to enable on-demand ISR on Atlas.In the meantime, we are excited to offer our users the opportunity to start utilizing this enhanced functionality on their headless WordPress websites.
How can I get started?
Make sure to check our documentation for detailed onboarding information.
Feedback
Should you have any feedback, please submit it using the our feedback form.