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.
By caching fallback routes per url we can greatly reduce the response time in case of heavy controllers, like requests to external services (e.g. strapi)
Here's an example how the timeline is currently in the fallback controllers if the page is available in a later controller
Once a url has had it's controller cached the timeline looks like this
This could be further optimised by caching the response to this url to prevent the external call in the first place.
But this is the responsibility of the controller making that external call.
Customisation to the cache duration can be done via the
rapidez.fallback_routes.cache_duration
config key.