[JAMES-3440] JMAP: Avoid ElasticSearch on critical reads

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.6.0
• Component/s: cassandra, elasticsearch, JMAP
• Assignee: Antoine Duprat
• Reporter: Benoit Tellier
• Created: 11/Nov/20 08:28
• Updated: 20/Nov/20 02:19
• Resolved: 20/Nov/20 02:19

Description

I wrote a little ADR: https://github.com/apache/james-project/pull/259

I am willing to improve the resiliency of the Distributed James JMAP deployments I have to manage.

On the James deployments I have to manage, ElasticSearch proves to be a pain point, both in term of performance and stability.

In order to enhence the service delivered to customers, I want to offer a good user experience given a degraded or down ElasticSearch on top of JMAP.

The way to do it will be to offer an optional Cassandra view for resolving common Email/query requests, involved on critical read operations (filter & comparators for sentAt).