News for hackers. Stuff that matters.

wallyqs

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/jetstream

- Bluesky's 'Introducing Jetstream': https://docs.bsky.app/blog/jetstream

Re:The Dhall Configuration Language on Thursday July 14, 2022 @08:23PM (#32103024)
Dhall has a lot of really cool ideas, it would be great to have semantic integrity checks on imports in other languages too.
Re:Connect: A Better gRPC on Thursday June 02, 2022 @05:47PM (#31600923)
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/2e744ec4bf7ce31... Internally requests are treated as NATS requests so you would get similar performance and latency as when using core NATS request/response.
Re:Build an Elixir Redis Server that’s faster than HTTP on Friday November 12, 2021 @02:05PM (#29203268)
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 sending headers now: https://docs.nats.io/nats-protocol/nats-protocol#protocol-me...

(disclaimer: I'm one of the NATS maintainers :) )

Re:Go modules have a v2+ problem on Friday September 11, 2020 @02:09PM (#24445581)
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
Re:RPC Olympics – The Search for the Perfect RPC Protocol on Thursday March 19, 2020 @05:15PM (#22631818)
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/nats-protocol
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/