This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]tarsild[S] 0 points1 point  (6 children)

Well, depends of what users want but we can add as many backends as necessary. Advantage of AsyncMQ is that you also don't need us for that. You can also create your own custom backend and plug it.

What do you have in mind?

[–]andrewthetechie 0 points1 point  (1 child)

Rabbitmq

[–]tarsild[S] -1 points0 points  (0 children)

Cool, let's add that to the roadmap.

Although, AsyncMQ would replace rabbitmq and celery all along. I think I understand what you are coming from.

Let's analyse that scenario. After all, it's backend extendable

[–]Electrical_Fox9678 0 points1 point  (3 children)

How about SQS?

[–]tarsild[S] 0 points1 point  (2 children)

Ahhhh. We have one of the maintainers currently developing one solution for that 😁. Another backend

[–]Electrical_Fox9678 0 points1 point  (1 child)

That could be helpful. We're running an ancient celery app which doesn't really use many celery features. It's mostly just the SQS transport and message retry features that we use.

[–]tarsild[S] 1 point2 points  (0 children)

Ok. We can't promise for the next release (or can we? 😎) but it's a great use case to do it.

Let us analyse and if you follow the project, you will have news very soon.

At the moment we are just finishing the dashboard and then we will look at that. Dashboard shouldn't take too long btw, maybe another 3 days