dramatiq VS sdk-java

Using something like Dramatiq [1] with Redis, writing a background job takes minutes, and can be deployed alongside an existing Python web app. There are probably JS equivalents.

I think Inngest could be a useful service, but the comparison felt off for me - it made me feel like this wasn't solving a real problem.

[1] https://dramatiq.io/

Dramatiq documentation

Hello everyone. We want to present you Taskiq: our new project that allows sending tasks using distributed queues. Conceptually it's similar to Celery or Dramatiq but with full asyncio and type hints support. Taskiq can send and execute async functions and has many integrations with different queue implementations.

I spent 3 years building a high scale crawler on top of Celery.

I can't recommend it. We found many bugs in the more advanced features of Celery (like Canvas) we also ran into some really weird issues like tasks getting duplicated for no reason [1].

The most concerning problem is that the project was abandoned. The original creator is not working on it anymore and all issues that we raised were ignored. We had to fork the project and apply our own fixes to it. This was 4 years ago so maybe things improved since them.

Celery is also extremely complex.

I would recommend https://dramatiq.io/ instead.

[1]: https://github.com/celery/celery/issues/4426

I have been using dramatiq lately (celery alternative) and so far I'm happy with it.

this is a more robust solution. https://dramatiq.io/

Dramatiq -> Just another celery?

How does this compare against Temporal/Cadence/Conductor? Does hatchet also support durable execution?

https://temporal.io/

Flawless sounds a lot like https://temporal.io/ .

I'm wondering if it has the same scalability concerns - sticking everything in Postgres is fine at small-ish scale, but what happens when you outgrow Postgres, either because you have higher availability requirements (can't handle primary DB restarts) or because of the sheer volume of the workload?

Temporal is a scalable and reliable runtime for durable Workflow Executions. It enables you to develop as if failures don't even exist. I started exploring it over the Christmas holiday and using it for a recently open-sourced project.

I have my eyes on https://temporal.io/ for similar purposes.

Check out temporal.io open source project for a much cleaner solution using Durable Execution abstraction.

Interesting to see Netflix featured both on StackStorm & https://temporal.io/ frontpages.

Our stack at Escape is written in multiple languages because each team has specific needs. We use TypeScript for its vibrant ecosystem, Python for cybersecurity research and Go for performance-sensitive tasks. To orchestrate cross-language task orchestration, we first developed a simple request-response protocol over HTTP, but it wasn't sustainable as the Escape codebase grew rapidly. We evaluated several technologies to replace our homegrown protocol, and two emerged as the most promising options: Connect and Temporal. The title gives it away, but the reason is far from obvious

I've put a lot of time into Airflow and feel similarly that it's a huge pain and a risk to rely on it. I've replaced it with Temporal (https://temporal.io/) and while I don't have the breadth of experience with the frameworks you listed, I do think Temporal is a great replacement for Airflow.

Just to confirm my understanding; would you consider at least part of your product offering to be similar to temporal.io [1]? Your examples are reminiscent of theirs.

[1] https://temporal.io/