June 12, 2026
Queue the drama
Show HN: Lightweight Task queue on Erlang/OTP, SQLite-backed, no overengineering
A one-person task app drops with big ‘keep it simple’ energy and commenters are already picking sides
TLDR: EZRA is a new one-file background job tool that promises reliable task handling without the usual setup headache. Commenters loved the simplicity and the clever compatibility trick, but quickly turned the thread into a rivalry match and a side debate over the creator refusing pull requests.
A new project called EZRA showed up on Hacker News with a very spicy promise: background jobs without the usual circus. The pitch is almost suspiciously simple — run one server, save everything in one file, and use the same client tools many developers already have. In plain English, it’s a way to make sure jobs like sending emails or processing slow tasks don’t vanish if something crashes. And the crowd immediately locked onto the vibe: finally, a tool that says no to bloat.
But, of course, the real show was in the comments. One person instantly invoked Oban, a popular rival in this space, basically asking, “So… is this inspired by the cool kid everyone already likes?” Another dropped a rival recommendation for people married to PostgreSQL workflows, turning the launch thread into a mini app showdown. Classic Hacker News: nobody can just say “neat,” they must also nominate three alternatives. Well, except for the user who literally just said “good” — arguably the funniest review in the whole thread.
The most delicious bit of drama came from the project’s house rules: it’s maintained by one author, and pull requests are not accepted. That line practically waved a red cape at the comment section. One reply advised the creator to just disable pull requests entirely to avoid the inevitable flood of people who won’t read. Meanwhile, others praised the clever trick of speaking Redis’s language without actually needing Redis. Translation: even the skeptics had to admit the shortcut was kind of slick.
Key Points
- •EZRA is a persistent task queue that keeps tasks visible until workers explicitly acknowledge completion.
- •EZRA is backed by SQLite and runs on Erlang/OTP, storing queue data in a local database file.
- •The system uses the Redis RESP3 protocol, allowing standard Redis clients in multiple languages to connect without requiring Redis.
- •The article provides a Docker-based quick start and Python examples using xadd, xreadgroup, and xack for producing and processing tasks.
- •Reported performance figures include ~2 KB memory per worker, ~20 MB baseline memory, and throughput ranging from ~15k–80k tasks/sec depending on storage hardware.