If you’d like to help make NATS and its resources better, here are some ways. Chances are, if you find a feature useful, others will too. This website pulls documentation from GitHub so once you update the readme on GitHub, changes will show up here as well.
Ways to Contribute
The best way to get started contributing to NATS is to read our Contributor's Guide. Here are some examples of how you can contribute:
- Report or Fix Bugs
- Add or Propose New Features
- Improve Our Documentation
- Add or Update Client Libraries
- Host a Meetup
- Improve this website
Please contact us with any other suggestions.
We work with a variety of companies to ensure NATS is delivered in a broad range of solutions used by our community
The ecosystem of companies using NATS varies from rapidly growing startups to some of the largest companies in the world.
"We considered a number of modern messaging platforms. NATS was the clear choice because it’s the highest-performance message broker we could find, and it solidly supports all the languages in our stack. Because of its clean design, it was easy for us to get up to speed with NATS and it gives us the scalability and responsiveness we need."
—Bill Chute, Acadiant Limited
"NATS has the same attributes that we love with Go - Simplicity and Performance. We build a lot of micro service APIs, and NATS is a great message system to glue these services together. We really feel that NATS is providing minimal configuration, minimal footprint and maximum performance and stability."
—David V. Wallin, CTO and Development Manager, AdXto Solutions AB
"NATS resonated with us because of its simplicity. We found the overhead of the team learning and configuring Rabbitmq to be a pain. This resulted in difficult debugging and testing. So, before developing any more services on top of rabbitmq, we decided to have a look around for different solutions, and decided NATS was the right solution for us."
—Andrew Mackenzie-Ross, CTO at HappyCo
"The simplicity and focus of NATS enables it to deliver superior performance and stability with a lightweight footprint. It has the potential of becoming the de-facto transport for microservice architectures and event driven systems in this new era."
—Asim Aslam, Creator of Micro
"We always come back to NATS for two reasons: speed and simplicity. NATS performance exceeds any demands that we could ever place on it, and it can be deployed and configured in seconds. This gives us the advantage of scale and the flexibility to meet our customers needs. Whether its interservice communication for microservices architectures or low-latency, highly-transactional applications, NATS is the backbone of our distributed systems."
—David Williams, Partner at Williams & Garcia
"NATS is clearly leading the messaging technology pack when it comes to performance, scalability, simplicity, and ease of use. These metrics made it the clear choice for our development team who are busy building our next-generation call-center platform."
—Leif Madsen - Director of Engineering, Product Development, AVOXI
"Tedious connection code, painful maintenance, and repeated failures of other messaging systems we tried persuaded us to try something else. We chose NATS to back our real time metrics, logging and alerting infrastructure because of the simple but powerful messaging semantics, simplicity, and great throughput."
—Ryan Neal, Head of Infrastructure at Netlify