Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Drop-in SQS replacement based on SQLite

github.com

Post reply on HN
Print view View original

141–150 of 171 posts

Re: Show HN: Drop-in SQS replacement based on SQLite

#141

Post by xrd »

memset wrote: post #24
yimpolo wrote: post #23

This is super cool! I love projects that aim to create simple self-hostable alternatives to popular services. I assume this would work without much issue with Litestream, though I'm curious if you've already tried it. This would make a great ephemeral queue system without having to worry about coordinating backend storage.

I haven't tried this with litestream! It will be worth exploring that as a replication strategy. The nice thing about queues is that backend storage doesn't really need to be coordinated. Like, you could have two servers, with two sets of messages, and the client can just pull from them round robin. They (mostly) don't need to coordinate at all for this to work. However, this is different for replication where we hav…

Since this is a single go binary I bet it would work perfectly with litestream. I use litestream in the exact same way with Pocketbase and it works perfectly (Pocketbase is also a single go binary). I'm going to give it a try and report back.

Re: Show HN: Drop-in SQS replacement based on SQLite

#142

Post by jpc0 »

PanMan wrote: post #102

Correct me if I’m wrong but: SQLite sounds like: runs on one server. While that will work most of the time, it won’t work 100% of the time. I don’t know the specifics, but I’m fairly sure if a queue server crashes, SQS will keep working, as stuff is redundant. So while it can work in a best case, this (probably) won’t have the same reliability as SQS has..

Does this even need to compete feature wise with SQS?

If it faithfully reproduces the SQS Api what could possibly stop me from using this product now (if he ever does hosted) and then switching to SQS if the scale is ever justified?

I'm all for a full suite of solutions targeting the same API. Can I run this thing on a single server with my dashboard app for the 3 person team I'm developing for and all that it cost them is per hour for tech support and server hardware and deloy my multi million user app on SQS but have effectively the same code.

Re: Show HN: Drop-in SQS replacement based on SQLite

#143

Post by michaelcampbell »

This is really pedantic, totally outside any actual functionality, and may be a me thing, but a trigger for me is seeing left-justified (or worse, centered), columns of numbers (eg: your number of messages column).

I'll grant it's small to infinitesimal, but you asked for feedback.

Re: Show HN: Drop-in SQS replacement based on SQLite

#144

Post by memset »

michaelcampbell wrote: post #143

This is really pedantic, totally outside any actual functionality, and may be a me thing, but a trigger for me is seeing left-justified (or worse, centered), columns of numbers (eg: your number of messages column). I'll grant it's small to infinitesimal, but you asked for feedback.

Hadn't even thought about that. Now I can't unsee it. Thanks for the suggestion.

Re: Show HN: Drop-in SQS replacement based on SQLite

#145

Post by [deleted] »

bigstrat2003 wrote: post #126
andrewstuart wrote: post #99

Earlier quoted context omitted.

Ugh I didn't see that. My enthusiasm has instantly waned. Why is AGPL needed? Just be MIT and make it easy for people, espefcially if you're not planning on monetising it. I won't use AGPL code just on principle.

Not gonna lie, man - this is just as obnoxious as when GPL zealots shit on someone's permissively licensed project because they think it should be GPL. The man has a right to use whatever license he wants.

[deleted]

Re: Show HN: Drop-in SQS replacement based on SQLite

#146

Post by gkbrk »

mtndew4brkfst wrote: post #124
crazysim wrote: post #81

Earlier quoted context omitted.

I think the vibe might be that this is something someone could use for production.

With no distribution model and built on SQLite, it certainly doesn't scream "production candidate" to me.

You know there are millions of production deployments of SQLite right? It's perhaps the most widely deployed database.

Re: Show HN: Drop-in SQS replacement based on SQLite

#147

Post by pc86 »

Kwpolska wrote: post #131
memset wrote: post #12

Earlier quoted context omitted.

Truthfully, I don't know yet - I haven't even built a paid/hosted version at all. It is related to my existing business in the sense that it deals with realtime data. But I started working this as something I wish existed as opposed to having some big VC strategy and pitch deck behind it. (Also, I appreciate all of your feedback on this a month ago! It was really helpful to encourage me to keep looking into this and…

Not every open source project needs to be monetized. Projects that were created to "scratch one's itch" tend to fare better than those built to make money. Devs put more love and less stress into them than into things they want to build a business out of. The monetization paragraph reads really weird, as if you believe HN is a community of VC-adjacent people looking for new ways to make money (it isn't), and talking…

There are plenty of people here not interested in the VC space, not interested in startups (in the pg sense of the word), and not strictly looking for new ways to wake money. But it's run by a VC firm. It's primary purpose is one part of a large funnel for getting new applicants to that VC firm. It is by definition VC-adjacent, and by extension many or perhaps even most people on here, certainly most of the people posting and commenting a lot, will be somewhat in that market as well. You can ignore that if you want at no risk to yourself but just declaring "it isn't" as objective incontrovertible fact is kind of silly when at the very least it's up for debate. But honestly whatever HN is or is not is a pretty irrelevant point to argue.

What isn't irrelevant, I think, is the accusation that monetizing something you've worked on is somehow exploiting it. If this brings value to people, and they can make money using it, or make more money using, the OP deserves to charge them for it if they want to. There's nothing wrong or exploitative about that. You are free to donate all your time and not charge anyone for anything but it's silly to frame someone charging for their work as an exploitation of either that thing or the people paying for it.

Re: Show HN: Drop-in SQS replacement based on SQLite

#148

Post by pc86 »

meiraleal wrote: post #118
Aeolun wrote: post #112

Earlier quoted context omitted.

I think the crux of the argument is that if you are not planning to monetize it, why stop other people from doing so?

AGPL don't stop nobody from monetizing anything, they just gotta make their modifications public.

If you're anywhere close to a technical or developer space it's pretty clear how making your entire codebase public could negatively impact a monetization strategy. So yeah you're right that AGPL doesn't explicitly prevent monetization (other than "pay us for the source code" stuff of course) but in practice nobody with a serious monetization strategy is going to be releasing all their code AGPL either.

Re: Show HN: Drop-in SQS replacement based on SQLite

#149

Post by samatman »

Kwpolska wrote: post #131
memset wrote: post #12

Earlier quoted context omitted.

Truthfully, I don't know yet - I haven't even built a paid/hosted version at all. It is related to my existing business in the sense that it deals with realtime data. But I started working this as something I wish existed as opposed to having some big VC strategy and pitch deck behind it. (Also, I appreciate all of your feedback on this a month ago! It was really helpful to encourage me to keep looking into this and…

Not every open source project needs to be monetized. Projects that were created to "scratch one's itch" tend to fare better than those built to make money. Devs put more love and less stress into them than into things they want to build a business out of. The monetization paragraph reads really weird, as if you believe HN is a community of VC-adjacent people looking for new ways to make money (it isn't), and talking…

> Not every open source project needs to be monetized.

Where was this claim made? I missed it.

> Projects that were created to "scratch one's itch" tend to fare better than those built to make money. Devs put more love and less stress into them than into things they want to build a business out of.

This project is based on SQLite, which is several people's livelihood. As a result, it's rock-solid, reliable, and available to all without fee or restriction.

So it's an odd choice of project to choose to express this sort of eminently debatable sentiment.

Re: Show HN: Drop-in SQS replacement based on SQLite

#150

Post by avinassh »

memset wrote: post #17
sgarland wrote: post #9

This looks great! How were you planning on tackling distributed?

This is a great question and something I've been thinking about a lot. Big picture: Each queue node can operate (mostly) independently, and this is good. As a consumer, I don't really care where my next message comes from, so I can minimize the amount of data that needs to have a "leader". The only data that needs to be synced is the list of queues, which doesn't change often. If one server is full, it should be able…

Have you considered libsql? It is a distributed SQLite database, written mostly in Rust. There is a go database/sql and GORM driver available - https://github.com/tursodatabase/libsql

disclaimer: I am one of the maintainers

Post reply on HN