Glad to find out what you've been up to! Very cool and I am excited to see where you take this.
Show HN: Drop-in SQS replacement based on SQLite
121–130 of 171 posts
Re: Show HN: Drop-in SQS replacement based on SQLite
#122The whole idea here is superlative. +1 for k8s, kubernetes, cloud native, self-hosted, edge-enabled at low cost, no cost. I ran rq and minio for years on k8s, but been watching sqlite as a drop-in-replacement since most of my work has been early stage at or near the edge. Private cloud matters. This is an enabler. We've done too much already in public cloud where many things don't belong. BTLE sensors are perfectly h…
rq as in Redis Queue?
I had assumed https://github.com/rqlite/rqlite
Re: Show HN: Drop-in SQS replacement based on SQLite
#123Tangential 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.
Honestly shows the capabilities of both:
- The dev for making it both fast & simple to understand
- Golang for making the codebase easy to follow
Re: Show HN: Drop-in SQS replacement based on SQLite
#124Why not use LocalStack? It has SQS and a lot of AWS services for testing/development. Well documented, open source. https://docs.localstack.cloud/overview/
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.
Re: Show HN: Drop-in SQS replacement based on SQLite
#125Could you elaborate why you didn't choose e.g. RabbitMQ? I mean you talk about AMQP and such, it seems to me, that a client-side abstraction would be much more efficient in providing an exit strategy for SQS than creating an SQS "compatible" broker. For example in the Java ecosystem there is https://smallrye.io/smallrye-reactive-messaging/latest/ that serves a similar purpose.
Where AWS is the likely migration path for an app if it needs to be scaled beyond dev containers, already having tested with an SQS workalike prevents rework.
The celery Backends and Brokers docs compare SQS and RabbitMQ AMQP: https://docs.celeryq.dev/en/stable/getting-started/backends-...
Celery's flower utility doesn't work with SQS or GCP's {Cloud Tasks, Cloud Pub/Sub, Firebase Cloud Messaging FWIU} but does work with AMQP, which is a reliable messaging protocol.
RabbitMQ is backed by mnesia, an Erlang/OTP library for distributed Durable data storage. Mnesia: https://en.wikipedia.org/wiki/Mnesia
SQLite is written in C and has lots of tests because aerospace IIUC.
There are many extensions of SQLite; rqlite, cr-sqlite, postlite, electricsql, sqledge, and also WASM: sqlite-wasm, sqlite-wasm-http
celery/kombu > Transport brokers support / comparison table: https://github.com/celery/kombu?tab=readme-ov-file#transport...
Kombu has supported Apache Kafka since 2022, but celery doesn't yet support Kafka: https://github.com/celery/celery/issues/7674#issuecomment-12...
Re: Show HN: Drop-in SQS replacement based on SQLite
#126Earlier 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.
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.
Re: Show HN: Drop-in SQS replacement based on SQLite
#127The whole idea here is superlative. +1 for k8s, kubernetes, cloud native, self-hosted, edge-enabled at low cost, no cost. I ran rq and minio for years on k8s, but been watching sqlite as a drop-in-replacement since most of my work has been early stage at or near the edge. Private cloud matters. This is an enabler. We've done too much already in public cloud where many things don't belong. BTLE sensors are perfectly h…
can you share more about the BTLE sensors talking with Apple Watch? I'm aware that BLE heartrate sensors are detected as 'Health Devices' if I want to connect to it, but what other sensors are you working with?
Re: Show HN: Drop-in SQS replacement based on SQLite
#128Congratulations! I also love writing AWS API-compatible services. That's why I did Dyna53 [1] ;P (I know, unrelated, but hopefully funny) [1] https://dyna53.io
This is an absolutely unhinged project idea. Great work
Re: Show HN: Drop-in SQS replacement based on SQLite
#129The only reason I use SQS is because how it's compatible with other AWS Services, I can have an S3 bucket whenever there's an upload I can send an SQS Message and I can have it trigger a lambda.
Re: Show HN: Drop-in SQS replacement based on SQLite
#130Tangential 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.