Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-22786

CacheService using local caching with distributed invalidations

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 9.3
    • Component/s: Cache, PubSub, Redis
    • Release Notes Description:
      Hide

      Invalidation cache has been rewritten to a better distributed architecture that improves performances.

      Show
      Invalidation cache has been rewritten to a better distributed architecture that improves performances.
    • Upgrade notes:
      Hide

      RedisCache has been removed because it is now redundant and less efficient than the new pubsub-based invalidations (which are also based on an underlying Redis).

      Show
      RedisCache has been removed because it is now redundant and less efficient than the new pubsub-based invalidations (which are also based on an underlying Redis).
    • Sprint:
      nxFG 9.3.3
    • Story Points:
      5

      Description

      Our distributed cache implementation is currently based on Redis. But our cache architecture is to store things in a central Redis server, which is not really efficient as it requires reads from Redis of a full object for every hit and writes to Redis of a full object for every change.

      The proper distributed cache architecture is to have each Nuxeo node have a local in-memory cache, with cross-instances invalidations based on the AbstractPubSubInvalidator that uses the PubSubService.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 2 days, 3 hours
                  2d 3h