[5.x] Use cache locks in static cache #10370
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This swaps the lock in the Static Cache middleware from a hardcoded file-based Symfony Lock to Laravel's cache-based atomic lock.
This will allow people that use a horizontal scaling approach to use a more appropriate cache driver for locks. e.g. Redis.
This will use the same
static_cache
cache store if it exists. DocsThis also moves the locking behavior to only around the writable bits. If there's a cached response available to be served, it will be served without waiting for the lock.