api-cache-invalidation

Cache invalidation detects backend data changes and triggers Next.js on-demand revalidation by incrementing a cache version. Use Laravel observers to bump the version counter when models update, then call Next.js revalidation endpoints to refresh ISR pages automatically.

Yes, this pattern is built specifically for Laravel and Next.js ISR setups. It combines backend observers that increment cache versions with frontend revalidation services, supporting core models like Menu, Product, Article, and Image across admin updates and data synchronization.

A hybrid cache strategy using both time-based and on-demand revalidation works best. Include the cache version in API responses, wire backend events to trigger Next.js revalidation calls, and use a 10-second fallback for automatic cache refresh.

A revalidation service bridges backend changes to Next.js ISR by triggering on-demand refreshes. The Skill implements this pattern alongside time-based fallback, so your cache stays synchronized without manual intervention across admin updates and data-change events.

Cache versioning increments a counter in your Laravel backend whenever data changes. The API includes this version in responses, and Next.js detects version changes to invalidate stale ISR pages, ensuring frontend content matches backend state.

A 10-second time-based fallback ensures cache refresh even if on-demand revalidation fails. This dual approach prevents indefinite stale content while prioritizing immediate invalidation for critical updates.