Why isnt delayed message plugin shipped with rabbitmq #293
-
What is the reason for delayed plugin not being shipped with the main package, requiring manual download installation during deployment or people to package their own fork? Delayed messages feature is quite commonly used in many service architectures. and current way of enabling could be better. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Because it has serious limitations very explicitly stated in the README, and it uses a data store that will be removed from RabbitMQ in a future 4.x release. A future version of Tanzu RabbitMQ may include a delayed publishing feature but not necessarily as an exchange type and not based on this plugin. For this reason, RabbitMQ Core Team no longer works on this plugin but we do accept contributions such as #291 and #292 to keep it compatible with new releases. There is also #229 where a reasonably complete design outline for those who are interested in developing a replicated version. |
Beta Was this translation helpful? Give feedback.
-
The process of installing this plugin is not particularly onerous:
In any case, the core team no longer actively works on this plugin and that won't change. This is not an essential messaging or streaming feature and the amount of effort required to rework the plugin in a way similar to #229 is too substantial to justify making the next generation open source. We do not, however, prevent others from contributing to this plugin and as #291, #292 demonstrate, it is not completely abandoned. Since RabbitMQ is open source software, those who need this plugin |
Beta Was this translation helpful? Give feedback.
Because it has serious limitations very explicitly stated in the README, and it uses a data store that will be removed from RabbitMQ in a future 4.x release.
A future version of Tanzu RabbitMQ may include a delayed publishing feature but not necessarily as an exchange type and not based on this plugin. For this reason, RabbitMQ Core Team no longer works on this plugin but we do accept contributions such as #291 and #292 to keep it compatible with new releases.
There is also #229 where a reasonably complete design outline for those who are interested in developing a replicated version.