nats.go
nats.go copied to clipboard
nats-io
PubOpt adding compression configuration
Feature Request
Publish publishes a message to JetStream. adding compression configuration
Use Case:
Proposed Change:
Who Benefits From The Change(s)?
Bandwidth and IOPS of the NATS-server
Alternative Approaches
This is not something I've looked a ton at fixing yet but the client already seems to bring a fair amount of baggage with it for deployment to small spaces. Have seen some chatter about eg breaking the encoded connections out to their own package over the last ~year I wonder if compression is something that kinda fits there.
Our challenge here would be what compression method? How do we interact with the other 40+ client libs?
I think compressing outside of the NATS go lib is reasonable here and can be adopted to many situations.
All of that being said we have been looking into auto-compression a bit for leafnode connections and possibly gateways and routes.
