[1.x] Improve Catch-up Caching #1406
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.
Previously,
CatchUpProcess
used a repository cache to ensure that each process instance was interacting with the matchingProjectionRepository
. However, the caching was tied up to the ID of the catch-up process, which eventually led to missing hits — when the steps of the process were processed on different servers.This changeset addresses the issue by using the projection type URL as a caching key, and moving the cache population to the initialization phase of the corresponding Bounded Context.
The library version is bumped to
1.7.7-SNAPSHOT.4
.