nats-server
https://github.com/nats-io/nats-server
Go
High-Performance server for NATS.io, the cloud and edge native messaging system.
Triage Issues!
When you volunteer to triage issues, you'll receive an email each day with a link to an open issue that needs help in this project. You'll also receive instructions on how to triage issues.
Triage Docs!
Receive a documented method or class from your favorite GitHub repos in your inbox every day. If you're really pro, receive undocumented methods or classes and supercharge your commit history.
Go not yet supported2 Subscribers
Add a CodeTriage badge to nats-server
Help out
- Issues
- NATS Cluster - Dynamically del node
- Consumer not receiving messages when power off and restart, consumer's ack floor is ahead of stream's last sequence [v2.10.14]
- Embedded nats servers with opt.LogFile have no logging
- Add support for inline configuration in CLI
- [ADDED] option to keep or remove js headers
- Dynamic append headers for clients messages
- Performance degradation with slow consumers [v2.9.20, v2.10.14]
- Exposing a WebSocket Handler for embeded NATS servers
- '408 Request Timeout' instead of '404 No Messages' from $JS.API.CONSUMER.MSG.NEXT.<stream>.<consumer> [v2.10.14]
- wildcards should have permissions with user
- Docs
- Go not yet supported