Details
Description
https://www.mail-archive.com/server-dev@james.apache.org/msg71462.html
A good long term objective for the PMC is to drop RabbitMQ in
favor of pulsar (third parties could package their own components using
RabbitMQ if they wishes...)
This means:
- Solve the bugs that were found during the Pulsar MailQueue review
- Pulsar MailQueue need to allow listing blobs in order to be
deduplication friendly. - Provide an event bus based on Pulsar
- Provide a task manager based on Pulsar
- Package a distributed server backed by pulsar, deprecate then replace
the current one. - (optionally) support mail queue priorities
While contributions would of course be welcomed on this topic, we could
offer it as part of GSOC 2022, and we could co-mentor it with mentors of
the Pulsar community (see [3])
[3] https://lists.apache.org/thread/y9s7f6hmh51ky30l20yx0dlz458gw259
Would such a plan gain traction around here ?
Attachments
Attachments
1.
|
Solve instable test for the pulsar mail queue |
|
Open | Unassigned |
|
||||||||
2.
|
Apache Pulsar mailqueue could support priorities |
|
Open | Unassigned | |||||||||
3.
|
Pulsar Event Bus implementation |
|
Open | Unassigned | |||||||||
4.
|
Dead letter policy for the Pulsar MailQueue |
|
Open | Unassigned |
|
||||||||
5.
|
Back Task manager components with Apache Pulsar |
|
Open | Unassigned | |||||||||
6.
|
Assemble a distributed James server backed by Pulsar |
|
Open | Unassigned | |||||||||
7.
|
Pulsar MailQueue: support deduplicating blob store |
|
Open | Unassigned |