[
https://issues.apache.org/jira/browse/JAMES-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3956.
-
Resolution: Duplicate
See https://issues.apache.org/jira/browse/JAMES-3996
> Redis Event
did a Proof Of Concept about that in the PR JAMES 3996
Redis event bus POC <https://github.com/apache/james-project/pull/2028
.
The POC is considered done to me, and I want to share the POC result to
James devs:
- It is *possible *(the POC worked!) to replace the Event bus user
notifications (ke
>> Following the context of the Jira ticket JAMES-3996 POC: Move RabbitMQ
> >> Event bus user notifications to Redis
> >> <
> >>
> https://issues.apache.org/jira/projects/JAMES/issues/JAMES-3996?filter=allopenissues
> >> (TLDR:
> >> we observed
s/JAMES-3996?filter=allopenissues
(TLDR:
we observed some annoying issues with RabbitMQ in a deployment and we think
it could be better to move at least the user notifications part of Event
Bus to Redis), I did a Proof Of Concept about that in the PR JAMES 3996
Redis event bus POC <https://github.c
d be better to move at least the user notifications part of Event
> Bus to Redis), I did a Proof Of Concept about that in the PR JAMES 3996
> Redis event bus POC <https://github.com/apache/james-project/pull/2028>.
>
> The POC is considered done to me, and I want to share the POC resu
r=allopenissues
> >
> > (TLDR:
> > we observed some annoying issues with RabbitMQ in a deployment and we
> think
> > it could be better to move at least the user notifications part of Event
> > Bus to Redis), I did a Proof Of Concept about that in the PR JAMES 3996
>
cts/JAMES/issues/JAMES-3996?filter=allopenissues>
(TLDR:
we observed some annoying issues with RabbitMQ in a deployment and we think
it could be better to move at least the user notifications part of Event
Bus to Redis), I did a Proof Of Concept about that in the PR JAMES 3996
Redis event bus POC
could be better to move at least the user notifications part of Event
Bus to Redis), I did a Proof Of Concept about that in the PR JAMES 3996
Redis event bus POC <https://github.com/apache/james-project/pull/2028>.
The POC is considered done to me, and I want to share the POC result to
Jame
sub maven module for Redis in backends-common
* Use a memory event bus for groups
* Use Redis for handling Pub/Sub
* Use
[lettuce|https://github.com/lettuce-io/lettuce-core]|https://github.com/lettuce-io/lettuce-core]
for the non-blocking Redis driver
* Update docs
> Redis Event
* Update docs
> Redis Event bus
> ---
>
> Key: JAMES-3956
> URL: https://issues.apache.org/jira/browse/JAMES-3956
> Project: James Server
> Issue Type: New Feature
> Components: eventbus
>
Maksim Meliashchuk created JAMES-3956:
-
Summary: Redis Event bus
Key: JAMES-3956
URL: https://issues.apache.org/jira/browse/JAMES-3956
Project: James Server
Issue Type: New Feature
Linagora VIETNAM.
Product owner for Team-Mail product.
Chairman of the Apache James project.
Mail: btell...@linagora.com
Tel: (0033) 6 77 26 04 58 (WhatsApp, Signal)
Le nov. 1, 2023 12:22 PM, de Maksim Meliashchuk Hi all! I'm planning to
implement a Redis event bus.
github.com/apache/
Hi all! I'm planning to implement a Redis event bus.
https://github.com/apache/james-project/tree/master/event-bus/api
I would be glad for any advice, and I would also be very grateful if
someone could open a ticket in Jira describing this task.
Thanks!
13 matches
Mail list logo
