Honker – Durable queues, streams, pub/sub, and cron scheduler in a SQLite file
1–10 of 69 posts
Re: Honker – Durable queues, streams, pub/sub, and cron scheduler in a SQLite file
#2Prior discussion a few days ago: https://news.ycombinator.com/item?id=47874647
Re: Honker – Durable queues, streams, pub/sub, and cron scheduler in a SQLite file
#3It’s an interesting approach and can be quite fun to use for new projects.
> How it works: honker polls SQLite’s PRAGMA data_version every millisecond. That’s a monotonic counter SQLite increments on every commit from any connection, journal mode, or process — a ~3 µs read for a precise wake signal.
Re: Honker – Durable queues, streams, pub/sub, and cron scheduler in a SQLite file
#4At the end it says: "pg-boss and Oban are the Postgres-side gold standards" -- but Oban supports SQLite now too https://github.com/oban-bg/oban
Re: Honker – Durable queues, streams, pub/sub, and cron scheduler in a SQLite file
#5"Idle cost is that one lightweight SELECT per millisecond per database — no page-cache pressure, no writer-lock contention, no kernel file watcher in the mix."
I think (respectfully) the LLM that probably wrote this overshot the mark here because busy-polling a select does not actually sound better to me than a "kernel file watcher".
Re: Honker – Durable queues, streams, pub/sub, and cron scheduler in a SQLite file
#6Reminds me of Litestack for Rails. Eventually, it was abandoned because Rails itself started going all out on SQLite.
Re: Honker – Durable queues, streams, pub/sub, and cron scheduler in a SQLite file
#7Reminds me of Litestack for Rails. Eventually, it was abandoned because Rails itself started going all out on SQLite. https://github.com/oldmoe/litestack
All in*
Re: Honker – Durable queues, streams, pub/sub, and cron scheduler in a SQLite file
#8"Idle cost is that one lightweight SELECT per millisecond per database — no page-cache pressure, no writer-lock contention, no kernel file watcher in the mix." I think (respectfully) the LLM that probably wrote this overshot the mark here because busy-polling a select does not actually sound better to me than a "kernel file watcher".
"one lightweight SELECT per millisecond"
This reminds me of the teenager who told her dad that she was just a tiny little bit pregnant.
Re: Honker – Durable queues, streams, pub/sub, and cron scheduler in a SQLite file
#9"Idle cost is that one lightweight SELECT per millisecond per database — no page-cache pressure, no writer-lock contention, no kernel file watcher in the mix." I think (respectfully) the LLM that probably wrote this overshot the mark here because busy-polling a select does not actually sound better to me than a "kernel file watcher".
[flagged]
Re: Honker – Durable queues, streams, pub/sub, and cron scheduler in a SQLite file
#10"Idle cost is that one lightweight SELECT per millisecond per database — no page-cache pressure, no writer-lock contention, no kernel file watcher in the mix." I think (respectfully) the LLM that probably wrote this overshot the mark here because busy-polling a select does not actually sound better to me than a "kernel file watcher".
Yeah, I had the same instinct - this feels very much like a "nice idea" but the execution falls short. I mean - busily banging on sqlite like this? Shit at that point just use Redis.