zeebe
bull
Our great sponsors
zeebe | bull | |
---|---|---|
6 | 50 | |
2,995 | 14,948 | |
1.9% | 1.0% | |
10.0 | 7.1 | |
6 days ago | about 1 month ago | |
Java | JavaScript | |
- | GNU General Public License v3.0 or later |
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.
zeebe
- Is there a product that can orchestrate running jobs?
-
Moving Config Docs From YAML to Markdown
You can Ctrl + F (or Command + F) your way through the file, but you have to know what you are looking for.
-
Back-end for sending out emails after a certain delay
For this purpose, it's the equivalent of using a sledge hammer to crack a walnut, but I think something like Zeebe could facilitate that
-
Do you use Model-Driven Engineering in your jobs?
I’m doing a lot of exploratory work with BPMN right now.
I think if your business is largely transactional (think Stripe), there is a lot of value to be had by framing your development as “business process automation”.
The term (and BPMN) has a lot of enterprise baggage, but some of the tools out there [0][1] are well suited to orchestrating services (and people where necessary) as a single automated process. The the ability to build that flow visually using BPMN, and then execute it in a workflow engine where you can monitor it, audit it, and optimize over time is pretty compelling.
Here’s an interesting read on the topic: https://www.infoq.com/articles/events-workflow-automation/
-
The Reactive Monolith – How to Move from CRUD to Event Sourcing
(I have no idea whether ES is used in temporal though… never looked at the code)
bull
-
Prioritizing Concurrent Requests: Queuing system to handle distributed processes and messages with NodeJS and Bull
To implement the solution with a queue, I used a package called 'Bull' (https://github.com/OptimalBits/bull). It's a library that helps with distributed job control, providing some very useful solutions for this type of work, such as background job processing, queues with priorities (FIFO, LIFO, and others), among other features. 'Bull' uses Redis for queue storage, so if your application crashes for any reason, once it's back online, it will continue executing the processes that are in the queue. In our case, we'll use the FIFO (First in, first out) queue solution, meaning priority based on arrival order.
-
How to use Job Queue to handle email sending in your Nestjs server
For Job Queue, NestJs provides a package named @nestjs/bull as an abstraction/wrapper on top of Bull, a popular, well-supported, high-performance Node. js-based Queue system implementation.
-
How do you handle queues in Node.js? Have you ever tried using pgboss?
I'm working on a large ETL project that involves handling queues for file integration. Currently, we are using Redis with Bull (https://www.npmjs.com/package/bull) for this purpose. However, to streamline our architecture and address security concerns, we are considering migrating the queue to PostgreSQL.
-
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 do I implement Heroku background processes?
This is a memory intensive process though and Heroku is OOM'ing with R14 errors. For this they recommend migrating intensive work like this to a Background Job via Redis, implemented in Bull and Throng
-
Infinite loop pattern to poll for a queue in a REST server app
I would use a job queuer like https://github.com/OptimalBits/bull
-
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.
-
Back-end for sending out emails after a certain delay
I would use Bull to implement it
This (or equivalent system) is what's usually used for what you're trying to do.
-
Blitz.js – The Missing Fullstack Toolkit for Next.js
Something like Bull might do the job (https://github.com/OptimalBits/bull)
What are some alternatives?
Bee-Queue - A simple, fast, robust job/task queue for Node.js, backed by Redis.
kue - Kue is a priority job queue backed by redis, built for node.js.
node-resque - Node.js Background jobs backed by redis.
Camunda BPM - Flexible framework for workflow and decision automation with BPMN and DMN. Integration with Quarkus, Spring, Spring Boot, CDI.
kogito-runtimes - This repository is a fork of apache/incubator-kie-kogito-runtimes. Please use upstream repository for development.
agenda - Lightweight job scheduling for Node.js
Flowable (V6) - A compact and highly efficient workflow and Business Process Management (BPM) platform for developers, system admins and business users.
bottleneck - Job scheduler and rate limiter, supports Clustering
better-queue - Better Queue for NodeJS
idoit - Redis-backed task queue engine with advanced task control and eventual consistency
The gist - BullMQ - Message Queue and Batch processing for NodeJS and Python based on Redis
RedisSMQ - A simple high-performance Redis message queue for Node.js.