Live data from Hacker News

Show HN: Lightweight Task queue on Erlang/OTP, SQLite-backed, no overengineering

github.com

1–10 of 24 posts

Show HN: Lightweight Task queue on Erlang/OTP, SQLite-backed, no overengineering

#1
Setting up Kafka or such enterprise oriented software with their clusters or dedicated servers is heavy and bothering enough that most small teams or indie hackers skip it entirely and making compromise to use in-memory queues.

I wanted something in between: a persistent queue that is simple to run (one binary, which makes one sqlite db), gets real fault isolation and crash recovery due to Elixir, easy to inspect (open ezra.db in any SQLite browser and see every task), and requires no new client library - it speaks the Redis Streams wire protocol, so any Redis client in any language just works out of the box.

Very short demo video: [https://www.youtube.com/watch?v=MLYyD3DVWmE]

Show HN: Lightweight Task queue on Erlang/OTP, SQLite-backed, no overengineering
github.com

Re: Show HN: Lightweight Task queue on Erlang/OTP, SQLite-backed, no overengineering

#8
post #7
post #3

Oban is really awesome, are you inspired by it?

Title said “no overengineering” so I doubt it.

I would argue that Oban isn't overengineered.

If so should we also consider PostgreSQL overengineered?

It's a shame OP decided to use Elixir as base, many ecosystems don't have mature task queues (e.g. for Rust I had to roll my own: simple_queue) so the space IMO would be more welcoming.

On OTP doubt anything can even make a dent in Oban user base.

Re: Show HN: Lightweight Task queue on Erlang/OTP, SQLite-backed, no overengineering

#10
post #7
post #3

Oban is really awesome, are you inspired by it?

Title said “no overengineering” so I doubt it.

Satisfied former Oban user here. Oban is engineered. Your use-case may be petty, though, like your comment.
Post reply on HN