[jira] [Closed] (JAMES-3440) JMAP: Avoid ElasticSearch on critical reads

["Benoit Tellier (Jira)" <se...@james.apache.org>]

     [ https://issues.apache.org/jira/browse/JAMES-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benoit Tellier closed JAMES-3440.
---------------------------------
    Fix Version/s: 3.6.0
       Resolution: Fixed

> JMAP: Avoid ElasticSearch on critical reads
> -------------------------------------------
>
>                 Key: JAMES-3440
>                 URL: https://issues.apache.org/jira/browse/JAMES-3440
>             Project: James Server
>          Issue Type: Improvement
>          Components: cassandra, elasticsearch, JMAP
>            Reporter: Benoit Tellier
>            Assignee: Antoine Duprat
>            Priority: Major
>             Fix For: 3.6.0
>
>
> 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). 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org