Conveyor MQ
The gist
Our great sponsors
Conveyor MQ | The gist | |
---|---|---|
2 | 26 | |
50 | 5,051 | |
- | 4.4% | |
0.0 | 9.7 | |
5 months ago | 5 days ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Conveyor MQ
We haven't tracked posts mentioning Conveyor MQ yet.
Tracking mentions began in Dec 2020.
The gist
-
Are there any generally accepted standards for inter-microservice communication? Or does everyone just go it their own?
I use bullmq with node
-
What is a good background scheduler?
BullMQ is a pretty solid choice: https://github.com/taskforcesh/bullmq It's the successor of Bull: https://github.com/OptimalBits/bull
-
How to schedule tasks in a Node.js app 🕙
BullMQ
-
First time building microservice-based application
For Node.JS you can use something like BullMQ (https://github.com/taskforcesh/bullmq) and then dispatch jobs to the message queue with your worker handling the jobs. You can read about an example for Bull MQ here (https://deadsimplechat.com/blog/best-nodejs-schedulers/#2-bull)
-
Is my health check endpoint good enough?
bullmq seems like an open issue
-
Help implementing Heroku Data For Redis (+bull & throng) / `ioredis`
In order to try and mitigate the OOMs. I read the Background Jobs in Node.JS with Redis blog post and implemented Heroku Data For Redis with ioredis, BullMQ and Throng,
-
Building a task queue, Part 1
The Node.js libraries BullMQ and Bee Queue are also infrastructure and interface. However, you typically have to use their interface.
-
How to manage data fetching independently from several data sources?
How to manage that kind of data fetching independently from several data sources? Do I need Message Queue for that? Maybe build individual microservice for each API-client?
-
How do I allow my express REST server to handle multiple concurrent requests (200-500) at the same time?
This is the ideal scenario for a redis message queue like BullMQ. You could even process that queue in a stand alone process automatically if needed.
-
Practical Benefits of an Event Driven Approach
At Woovi we use bull for distributed jobs and messages using Redis. If you are starting a fresh codebase, or moving to event driven approach, we recommend to use bullmq which is a modern version of bull.
What are some alternatives?
bull - Premium Queue package for handling distributed jobs and messages in NodeJS.
Bee-Queue - A simple, fast, robust job/task queue for Node.js, backed by Redis.
better-queue - Better Queue for NodeJS
RedisSMQ - A simple high-performance Redis message queue for Node.js.
kue - Kue is a priority job queue backed by redis, built for node.js.
bree - Bree is a Node.js and JavaScript job task scheduler with worker threads, cron, Date, and human syntax. Built for @ladjs, @forwardemail, @spamscanner, @cabinjs.
node-resque - Node.js Background jobs backed by redis.
rsmq - Redis Simple Message Queue
agenda - Lightweight job scheduling for Node.js
p-throttle - Throttle promise-returning & async functions
growthbook - Open Source Feature Flagging and A/B Testing Platform