HNHacker News
TopNewBestAskShowJobs

ent1c3d

27 karma · joined August 25, 2024

submissionscomments
ent1c3d··on Show HN: Lightweight Task queue on Erlang/OTP, SQLite-backed, no overengineering
oh, that's seems very nice project! I just wonder what it uses as storage/where it saves the tasks?
ent1c3d··on Show HN: Lightweight Task queue on Erlang/OTP, SQLite-backed, no overengineering
You perfectly got the point - building and maintaining SDKs for all popular languages is very time-consuming, and it also adds a barrier between your project and potential users, who have to get familiar with it, install it, and so on.

But, for sure, having your own SDKs has advantages too - you don't depend on anyone else's protocol decisions, have less dependency, eyc.

Btw, the first time I saw one company use another company's SDK, which I really liked, was in 2023, when DeepSeek used OpenAI's SDK and still think it was brilliant.

ent1c3d··on Show HN: Lightweight Task queue on Erlang/OTP, SQLite-backed, no overengineering
Maybe kinda shameful, but have to admit I just heard about Oban from you - and it seems an amazing thing. thanks for mentioning it!

Re inspiration: no direct inspiration really, just needed this tool myself for my own projects. But I guess this project as my engineering taste was kind of influenced/validated by bright minds like Richard Hipp, Joe Armstrong, and Derek Sivers

ent1c3d··on Show HN: Lightweight Task queue on Erlang/OTP, SQLite-backed, no overengineering
Thanks, really glad you liked the idea to use redis protocol!

as an answer: tare actually two ways to run it. As a standalone binary, it's one process you run(you can easily run it via docker too) on its own(which speaks on Redis protocol over TCP) - and any language connects to it like a Redis server.

Or, if you're on Elixir, you can skip the separate process entirely and add it directly to your app's supervision tree - it runs inside your own app's process, no network hop, just function calls.

ent1c3d··on Show HN: Lightweight Task queue on Erlang/OTP, SQLite-backed, no overengineering
that's a smart point. Just did it, thanks!