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.
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.
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...
- NATS JetStream docs: https://docs.nats.io/nats-concepts/jetstream
- Bluesky's 'Introducing Jetstream': https://docs.bsky.app/blog/jetstream