james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benoit Tellier (Jira)" <server-...@james.apache.org>
Subject [jira] [Commented] (JAMES-2813) Implement a distributed task manager
Date Fri, 27 Sep 2019 04:21:00 GMT

    [ https://issues.apache.org/jira/browse/JAMES-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16939103#comment-16939103

Benoit Tellier commented on JAMES-2813:

https://github.com/linagora/james-project/pull/2722 is an attempt at restructuring tasks maven

Here are some decisions I  would like to enforce:

 - Split API and memory implementation

 - The implementation imports many things into caller dependencies (event sourcing + its memory
 - We can not enforce that callers relies on the API and not on some memory implementation
 - Hexagonal architecture through maven structure

 - Rename james-server-task into james-server-task-memory

 - Move task related projects into a `/server/task` folder

Rationals: this pollutes the server directory structure, a bit of order will be nice.

> Implement a distributed task manager
> ------------------------------------
>                 Key: JAMES-2813
>                 URL: https://issues.apache.org/jira/browse/JAMES-2813
>             Project: James Server
>          Issue Type: Task
>            Reporter: Matthieu Baechler
>            Priority: Major
> Following JAMES-2272, we now would like to handle tasks at a cluster level.
> For that, we intend to use a combination of Event Sourcing for keeping track of Tasks
submitted and RabbitMQ for dispatching the tasks in the cluster.

This message was sent by Atlassian Jira

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

View raw message