Job queue #78

New issue

Closed

opened 2018-06-23 16:49:22 +00:00 by elegaanz · 1 comment

elegaanz commented

2018-06-23 16:49:22 +00:00

(Migrated from github.com)

I think we could use the lapin-futures crate (and RabbitMQ as a backend), and see if we can integrate it nicely with Rocket (with a Fairing and/or a FromRequest impl). But if you have a better solution, feel free to propose it.

Now that the models are separated from the rest of the app, we can implement a job queue, to run background processes (like fetching profiles or articles, without blocking the response sent to the user). I think we could use the `lapin-futures` crate (and RabbitMQ as a backend), and see if we can integrate it nicely with Rocket (with a `Fairing` and/or a `FromRequest` impl). But if you have a better solution, feel free to propose it.

elegaanz commented

2018-07-26 16:03:06 +00:00

(Migrated from github.com)

Finally chose an in-process queue, based on threads, to make Plume really simple to install.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Plume/Plume#78

No description provided.

Rows
Columns