SaaS Metrics
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
A persistent, simple-to-run, fault-isolated, easy-to-inspect alternative to complex enterprise message brokers (like Kafka) and volatile in-memory queues, specifically for small teams and indie hackers.
View Origin LinkProduct Positioning & Context
AI Executive Synthesis
A persistent, simple-to-run, fault-isolated, easy-to-inspect alternative to complex enterprise message brokers (like Kafka) and volatile in-memory queues, specifically for small teams and indie hackers.
This product addresses a clear market gap for persistent queuing without the operational overhead of Kafka-like systems. Small teams and indie developers face a dilemma: over-engineer with complex distributed systems or compromise with volatile in-memory solutions. The product's positioning leverages SQLite for persistence and Redis Streams protocol for client compatibility, significantly lowering the barrier to entry. This targets a segment prioritizing simplicity, rapid deployment, and reduced infrastructure burden, enabling faster iteration and resource allocation away from infrastructure management. The Erlang/OTP foundation implies inherent fault tolerance, a critical feature often sacrificed in simpler alternatives. This could capture significant market share from teams currently making compromises.
Related Ecosystem & Alternatives
Discover adjacent products, open-source repositories, and developer tools sharing similar technical architecture.
Deep-Dive FAQs
What is Lightweight Task queue on Erlang/OTP, SQLite-backed, no overengineering?
Lightweight Task queue on Erlang/OTP, SQLite-backed, no overengineering is analyzed by our AI as: A persistent, simple-to-run, fault-isolated, easy-to-inspect alternative to complex enterprise message brokers (like Kafka) and volatile in-memory queues, specifically for small teams and indie hackers.. It focuses on This product addresses a clear market gap for persistent queuing without the operational overhead of Kafka-like systems. Small teams and indie deve...
Where did Lightweight Task queue on Erlang/OTP, SQLite-backed, no overengineering originate?
Data for Lightweight Task queue on Erlang/OTP, SQLite-backed, no overengineering was aggregated directly from the Hacker News community ecosystem, representing raw developer and early-adopter sentiment.
When was Lightweight Task queue on Erlang/OTP, SQLite-backed, no overengineering publicly launched?
The initial public indexing or launch date for Lightweight Task queue on Erlang/OTP, SQLite-backed, no overengineering within our tracked developer communities was recorded on June 13, 2026.
How popular is Lightweight Task queue on Erlang/OTP, SQLite-backed, no overengineering?
Lightweight Task queue on Erlang/OTP, SQLite-backed, no overengineering has achieved measurable traction, logging over 62 traction score and facilitating 10 recorded discussions or engagements.
Which technical categories define Lightweight Task queue on Erlang/OTP, SQLite-backed, no overengineering?
Based on metadata extraction, Lightweight Task queue on Erlang/OTP, SQLite-backed, no overengineering is categorized under topics such as: Erlang/OTP, SQLite-backed, fault isolation, crash recovery.
What are some commercial alternatives to Lightweight Task queue on Erlang/OTP, SQLite-backed, no overengineering?
Our semantic intelligence engine identifies potential commercial alternatives in the SaaS space, such as Velo 3.0, which offers overlapping value propositions.
How does the creator describe Lightweight Task queue on Erlang/OTP, SQLite-backed, no overengineering?
The original author or development team describes the product as follows: "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 comp..."
Community Voice & Feedback
Maybe this says more about me than your project, but I find the use of implementing this with the Redis Streams wire protocol very interesting and creative. Being able to leverage the surface area of existing client SDKs should really help adoption and reduce what you have to maintain in order to widely integrate.I agree that in many areas there often is not much in-between "roll yourself in-memory" and "enterprise grade maxed out scalability focus".
[flagged]
This is really cool! I built something very similar only I replicated the AWS sqs protocol instead.https://github.com/poundifdef/smoothmq
> This project is maintained by a single author and pull requests are not acceptedSave yourself the headache of people not reading this and just disable pull requests in the repo settings
Congrats on the launch. Using the Redis protocol was a pretty clever choice. Does it have to run as a stand-alone server?
good
This is nice. For those wanting to stay on Postgres for DAG type of workflows, check out pgmq based PgFlow: https://github.com/agoodway/pgflow
Oban is really awesome, are you inspired by it?
[flagged]
Discovery Source
Hacker News Aggregated via automated community intelligence tracking.
Tech Stack Dependencies
No direct open-source NPM package mentions detected in the product documentation.
Media Tractions & Mentions
No mainstream media stories specifically mentioning this product name have been intercepted yet.
Deep Research & Science
No direct peer-reviewed scientific literature matched with this product's architecture.