Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Abandoned
-
3.0.0
-
None
-
Unknown
Description
Currently, if two requests for the same cache key come in simultaneously, both requests will execute the route decorated with the cache policy. If this route includes expensive calculations/integrations this may be undesirable. Instead, only the first request should kick off the real route, and the second should block on the cache read until the result of the first route has entered the cache.
Spring, for example, supports this with the "sync" parameter on @Cacheable.