Deployment Options

Nuxeo and Redis


Nuxeo provides a Redis integration via the nuxeo-core-redis bundle.

The idea is that, at least for now, Redis is not a hard requirement for running the Nuxeo Platform; We simply use Redis as a backend to provide alternate implementation of some services inside the platform. However, we do provide these implementations because we think they can be useful.

Nuxeo uses Redis to store transient data, after a normal cluster shutdown, the content of Redis can be flushed (erased). Note however that Nuxeo can not work with a Redis configured as LRU cache, there should be no eviction under memory pressure, hopefully this is the default policy of Reds.


Nuxeo Core Cache

Nuxeo Core Cache provides a service to declare and use caches. This cache system:

  • is used in Nuxeo Directories (caching directories entries)
  • is used in UserManager (caching principals)
  • is used in Nuxeo Drive (caching synchronization roots)
  • can be used in your custom code 

The Cache has a default "in memory" implementation, but nuxeo-core-redis provides another implementation that allows:

  • To have out of JVM memory cache storage. It opens the way to have big caches without hurting the JVM.
  • To share the same cache between several Nuxeo nodes. In cluster mode this can increase cache efficiency.
  • To manage cluster wide invalidations. Updating the user on one node will impact the central cache: all nodes see the exact same data.

You can configure the backend storage on a per cache basis: Directory A could use Redis while directory B could use in memory.

Work Manager

The WorkManager handles asynchronous jobs:

  • Schedule Jobs and store them in queues
  • Assign execution slots to queues 
  • Execute the jobs

In the default implementation, job queues are in the JVM memory. But this model has some limitations:

  • Stacking a lot of jobs will consume JVM Memory
  • In cluster mode each Nuxeo node maintains its own queue
  • When a Nuxeo server is restarted, all the queued jobs are lost

nuxeo-core-redis provides an alternate implementation of the queuing system based on Redis:

  • Jobs are then stored outside of JVM memory. That's why Work have to be serializable: they are serialized and stored inside Redis.
  • Jobs can be shared across cluster nodes. This allows to dedicate some nodes to some specific processing.
  • Jobs survive a Nuxeo restart. When Redis persistence is activated, the jobs even survive a Redis restart.

Lock Manager

By default Lock managed on documents are stored inside the repository backend. When the locking system is heavily used, it can create a lot of very small transactions against the database backend.

nuxeo-core-redis provides a Redis-based implementation of the locking system that is resilient as the database implementation, but easier to scale.

VCS Row Cache Invalidation

Since 7.4 () it is possible to manage VCS row cache invalidations with Redis instead of using the database.

To do so you need to change the repository configuration default-repository-config.xml.nxftl to add the following line inside the repositoryelement:


Since 8.1 and 7.10-HF02 you only need to add this option in the nuxeo.conf


Transient Store

The RedisTransientStore is a Redis-based implementation of the Transient Store.

It is the one used by the default Transient Store if Redis is enabled.

It allows the parameters associated to the stored blobs to be shared across cluster nodes.


5 months ago manonlumeau Relocated assets to fit new URL structure for 710 - fix
3 years ago Benoit Delbosc 14 | dd a note about redis usage and memory evictio
3 years ago Benoit Delbosc 13
3 years ago Nicolas Chapurlat 12
4 years ago Solen Guitter 11 | Add Transient Store section
4 years ago Manon Lumeau 10 | Formatting
4 years ago Benoit Delbosc 9
4 years ago Benoit Delbosc 8
4 years ago Benoit Delbosc 7 | Add a note about VCS row invalidation
4 years ago Manon Lumeau 6
5 years ago Solen Guitter 5
5 years ago Solen Guitter 4
5 years ago Solen Guitter 3
5 years ago Thierry Delprat 2
5 years ago Thierry Delprat 1
History: Created by Thierry Delprat

We'd love to hear your thoughts!

All fields required