dramatiq VS walex

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?

The WAL CDC approach: https://github.com/cpursley/walex?tab=readme-ov-file#publica...

CREATE PUBLICATION news_item FOR TABLE news WHERE (topic IS "AAPL");

What do you mean testing with processes?

I won't suggest these are the best written tests, but I test various processes, supervisors, etc like this:

https://github.com/cpursley/walex/blob/master/test/walex/sup...

You don’t send the entire WAL, just what you subscribe to - and you can even filter via SQL: https://github.com/cpursley/walex?tab=readme-ov-file#publica...

What we do is much if the business logic in Postgres. But then there’s all the other stuff like external integrations, etc.

We handled that by having an Even system built on the Postgres WAL that we use like a callback system.

I put together a little library in Elixir (that originally started out as forked Supabase realtime) for this:

https://github.com/cpursley/walex

Recently added the ability to configure WalEx to forward events to webhooks or EventRelay (so you don’t need to know Elixir).

If you're using Elixir, check out https://github.com/cpursley/walex

I've actually been thinking about turning this idea into a product where you can just point it at your postgres database and select the tables you want to listen to (with filters, like you describe). And have that forwarded to a webhook (with possibility of other protocols).

I'd love to hear folks thoughts on that (and if it would be something people would pay for).

Neat, this is the pattern I've been thinking about for a while now. Also glad to see this is Elixir based.

I've been using https://github.com/cpursley/walex (basically a fork of cainophile via a fork for subabase) to listen to Postgres changes in Elixir.

https://github.com/cpursley/walex

Which is based on WAL logs and doesnt have the same limitations.

Great writeup, just added this to the WalEx readme:

https://github.com/cpursley/walex

(WalEx is an Elixir lib for listening to the WAL and perform callback-like actions with the data)

Very cool.

I'm using Elixir to listen to change events via https://github.com/cpursley/walex (which I basically ripped off from Supabase).