wallyqs

4 ms·

1.
by wallyqs 1y ago
Bluesky's project name is 'Jetstream' and NATS.io persistence engine is `JetStream` (camel case), which can be confusing but name not exactly the same. - NATS JetStream docs: https://docs.nats.io/nats-concepts
2.
by wallyqs 4y ago
Dhall has a lot of really cool ideas, it would be great to have semantic integrity checks on imports in other languages too.
3.
by wallyqs 4y ago
Put out an example of using it to switch the transport so that it is over NATS instead, this works now thanks to the interop with net/http package: https://github.com/wallyqs/connect-go/commit/2e744ec4bf7
4.
by wallyqs 5y ago
NATS has a similar protocol to Redis and optimized for this use cause of doing pub/sub based low latency Request/Response instead of HTTP. The payload is opaque so you can use msgpack if needed, and the protocol also supports send
5.
Introducing go_test.mod: How to avoid meta test dependencies across Go modules(dev.to)
4 points by wallyqs 5y ago|0 comments
6.
by wallyqs 6y ago
It has gotten much better but in our project we got bitten by this. I gave a talk about it at GoSF last year if looking for some Go v2 modules schadenfreude :) https://www.youtube.com/watch?v=8xAaZDSDWOc
7.
by wallyqs 7y ago
For speed, NATS.io also has RPC semantics and protocol is fairly straightforward like Redis: https://docs.nats.io/developing-with-nats/sending/request_re... || https://docs.nats.io/nats-protocol&#x
8.
by wallyqs 7y ago
I'm one of the NATS maintainers though have been using the project for several years. Most of the community is more active in the Slack channel: https://slack.nats.io/
9.
CNCF to host NATS as incubation-level project(cncf.io)
6 points by wallyqs 9y ago|0 comments