RabbitMQ integration

[jakub.skowron]

Hi,

Have any of you succesfully done integration of espocrm with rabbitmq ? We have a lot of processes and database quees degrades db performance. I would be grateful for sharing your thoughts and advice on how to do it right.

[esforim]

Haven't seen anyone on the forum talked about it yet so any integration must have been done privately. I think you are on your own at the moment, the pioneer.

Reading through RabbitMQ website, I'm still not sure what it do.

[yuri]

I think we will eventually implement it. It should not be difficult to do now as we have an interface for job scheduling. One would need to bind a custom implementation to use RabbitMQ instead of internal jobs. It will work only for regular jobs, but not for scheduled jobs.

[partomas]

I'm excited about https://github.com/espocrm/espocrm/issues/3724 and looking forward to EspoCRM 10.1. Does anyone have an estimate of when 10.1 might be released?

I also have a question regarding the planned RabbitMQ integration.

Will RabbitMQ be intended only for internal EspoCRM job processing/distribution, or will it also be possible to use it from custom integrations, workflows, custom code, etc.?

For example, it would be very useful if custom EspoCRM logic could publish messages/events to RabbitMQ and also consume messages from custom queues.

It would be great to be able to use RabbitMQ as a full messaging layer for integrations, rather than only as an internal job queue.

[yuri]

It's planned to be released in about 2-3 months. Everything that this implementation does is described in the GitHub issue.

As it describes, it's for jobs only. Jobs are not something internal only. You can utilize jobs for custom purposes. For example send emails in a specific job queue. Workflows already use jobs for parallel processing.

There will be also an Event framework to communicate between Espo process instances with Redis.

This functionality won't be revised for adding more things, as we've already switched the focus to another (very important) subject.

> It would be great to be able to use RabbitMQ as a full messaging layer for integrations, rather than only as an internal job queue.

I don't think that we really need to have it and maintain it. A developer can easily implement it for their particular use case. E.g. a worker subscribed to RabbitMQ, creating jobs that are picked up by Espo. Or creating BPM signals.