Skip to content
This repository has been archived by the owner on Nov 21, 2020. It is now read-only.

Consider using RabbitMQ #223

Closed
erdenezul opened this issue Nov 12, 2018 · 1 comment
Closed

Consider using RabbitMQ #223

erdenezul opened this issue Nov 12, 2018 · 1 comment

Comments

@erdenezul
Copy link
Contributor

RabbitMq could be used in background process and subscriptions.
htstps://github.com/cdmbase/graphql-rabbitmq-subscriptions

@shinebayar-g
Copy link
Contributor

I'd definitely suggest to reconsider redis usage here. Redis is general purpose key value store, it has basic support for message broker. If we use RabbitMQ or any other MQ broker we'd have many advantages over using redis here. However if we ever come to make this decision I'd suggest newer cloud native technologies like NATS.io or NSQ.io.
NATS.io - Is now CNCF hosted project which has promising future.
NSQ.io - Is more mature and trusted by industry biggies.

batamar added a commit to erxes/erxes-widgets-api that referenced this issue Jul 31, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants