[UNOMI-166] Experiment : introduce a back-end cache for the ElasticSearch persistence manager

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Won't Do
• Affects Version/s: unomi-1.3.0-incubating, unomi-1.4.0
• Fix Version/s: unomi-3.0.0
• Component/s: unomi(-core)
• Assignee: Serge Huber
• Reporter: Serge Huber
• Created: 17/Feb/18 17:23
• Updated: 21/Oct/22 13:34
• Resolved: 21/Oct/22 13:34

Description

Given the slow performance of the ElasticSearch back-end for load and save operations, it would be an interesting idea to look at using a back-end cache to absorb the load until ElasticSearch can process the requests. 

Also, introducing such a cache would make it possible to use bulk processing to process save requests, while still making the saved objects immediately available since they are immediately available in the cache.

The cache could be implemented using Hazelcast, which is already available since it is used by Karaf Cellar.

Based on the result of this experiment the cache could be activated by default (if no serious issues are found during the experiment), or removed and replaced by some other solution.