Live data from Hacker News

Show HN: Drop-in SQS replacement based on SQLite

github.com

131–140 of 171 posts

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

#131
post #12

> In terms of monetization, the goal is to just have a hosted queue system. I believe this can be cheaper than SQS without sacrificing performance. Just as Backblaze and Minio have had success competing in the S3 space, I wanted to take a crack at queues. are you monetizing this as a separate business from: https://www.ycombinator.com/companies/scratch-data

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 about how you plan to exploit your new project is mandatory (it isn't either).

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

#132
post #114

Tangential but I looked at the codebase - because I like to imagine I can code (I can’t) - and for a laymen, I could follow the code. Makes me think quite positively of go lang and of the dev for designing in such a way. Can understand why teams like it because of easier maintenance Quite elegant from my uneducated pov.

That's the beauty of Go, generally, and why I immediately became attracted to it. The code is supremely readable because it enforces a style guide, and doesn't allow much magic. A number of people don't like it for limiting their expression and abilities, which I understand that feeling too. But as a middle aged programmer I realized that readability trumps conciseness and cleverness in the long run.

I can't remember who said it but I remember hearing that a good go Dev and a new go Dev should be able to produce generally similar code in order for maintainability. I do like playing with go, it's sits in a nice little playground in my head, mostly thanks to the compile times I think.

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

#134

Earlier quoted context omitted.

That's the beauty of Go, generally, and why I immediately became attracted to it. The code is supremely readable because it enforces a style guide, and doesn't allow much magic. A number of people don't like it for limiting their expression and abilities, which I understand that feeling too. But as a middle aged programmer I realized that readability trumps conciseness and cleverness in the long run.

I can't remember who said it but I remember hearing that a good go Dev and a new go Dev should be able to produce generally similar code in order for maintainability. I do like playing with go, it's sits in a nice little playground in my head, mostly thanks to the compile times I think.

Two experienced Go devs tackle the same task, and their code will look almost identical.

Two experienced Rust devs tackle the same task, and their solutions will be worlds apart.

(I write both, but I do love Go for its simpleness)

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

#135

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.

There’s more production systems on this planet running on a single node than ones running in a distributed setup. And SQLite is a rock solid database, deployed in more places than Postgres. The only thing here that could be taken when weighing production readiness would be the maturity and stability of this project itself.

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

#136
post #41

Earlier quoted context omitted.

What's the point of AGPL though? The enterprises with the budget for self hosting this sort of software usually have requirements and scale beyond what SQLite can offer out of the box.

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.

Provoking this sort of response is the best feature of the AGPL. I love it.

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

#137

The goals are a little different but I think it's worth pointing out ElasticMQ. I use it simulate sqs in a docker environment. https://github.com/softwaremill/elasticmq

We use ElasticMQ to have an SQS compatible service for local development. We use it with docker-compose locally. In our remote envs we use SQS.

So far I had not problems with ElasticMQ.

I'm much intrigued by the small LOC count of SmoothMQ. When I compare it to ElasticMQ it's much smaller (probably by using sqlite's features).

https://github.com/softwaremill/elasticmq

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

#139
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…

[dead]

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

#140
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…

> HN is a community of VC-adjacent people looking for new ways to make money

it kinda is. There are all sorts of people here, but HN is owned by YC, a well known VC fund. That doesn't mean that everyone here is one, but it certainly influences the community here.

> and talking about how you plan to exploit your new project is mandatory

it's not mandatory but it's a frequently asked question. OP might as well answer it while they have the mic.

Post reply on HN