How does this compare with Bull?

[sharathprabhal]

I'm a long time user of Bull. We've been relatively happy but it's been causing issues recently , especially for long running jobs. Do you have any documentation on how sidequest compares with Bull in terms of feature parity and performance?

[merencia]

Hey @sharathprabhal, we haven’t published a full comparison doc yet. It’s definitely on our roadmap, but right now we are focused on building solid features and improving the Sidequest experience.

That said, there are a few conceptual differences worth highlighting:

• BullMQ enqueues plain JSON objects. Your worker receives a raw payload and has to interpret it.
• Sidequest lets you define jobs by extending a Job class. You enqueue an instance, and on execution, you get a full class instance with methods, state, and proper encapsulation.

Also:

• Job persistence: In BullMQ, Redis only persists jobs if it is explicitly configured to do so. Otherwise, you risk losing data on restarts or crashes.
  Sidequest jobs are persisted by default in a proper database like PostgreSQL, MySQL, SQLite, or MongoDB.

• No vendor lock-in: You are not forced to run Redis. Sidequest works with databases you are likely already using, which helps reduce operational cost and complexity.

If you have specific issues with Bull, especially around long-running jobs, feel free to share. We would be happy to dig into how Sidequest might help.