200ebbd47e
This is a proposal to add schema, timestamps and unique ids to events. For now just JS ones but I propose to do these for all events the server sends that might be end user consumed. These exist to help the user identify a message even if it was sent to a 3rd party system, the schema will be translatable to a well known url like https://nats.io/schames/jetstream/event/v1/obs_ack.json or to another wll known identifier like a NATS subject name We'd publish JSON schema documents at these well known locations describing each key and so forth
NATS is a simple, secure and performant communications system for digital systems, services and devices. NATS is part of the Cloud Native Computing Foundation (CNCF). NATS has over 30 client language implementations, and its server can run on-premise, in the cloud, at the edge, and even on a Raspberry Pi. NATS can secure and simplify design and operation of modern distributed systems.
Documentation
- Official documentation
- FAQ
- Watch a video overview of NATS to learn more about its origin story and design philosophy.
Contact
- Twitter: Follow us on Twitter!
- Google Groups: Where you can ask questions
- Slack: Click here to join. You can ask question to our maintainers and to the rich and active community.
Contributing
If you are interested in contributing to NATS, read about our...
Security
Security Audit
A third party security audit was performed by Cure53, you can see the full report here.
Reporting Security Vulnerabilities
If you've found a vulnerability or a potential vulnerability in the NATS server, please let us know at nats-security.
License
Unless otherwise noted, the NATS source files are distributed under the Apache Version 2.0 license found in the LICENSE file.