NATS uses cookies to ensure you get the best experience on our website. Continuing to use this site assumes compliance with our Privacy Policy.

Guest Post: NATS on Autopilot - How the team at Joyent simplify complex applications

By: Wyatt Preul - Date: September 29, 2017

Here on the product team at Joyent, we enjoy making sophisticated applications easy to deploy and manage. For us, that means containerizing components, automating them with ContainerPilot and the Autopilot Pattern. This typically means that we are containerizing the components that comprise our solutions with Docker and are using a service discovery catalog like Consul. Up until this year, we didn’t have a working solution to solve the message queuing problem. Read More…

NATS and Tracing: Keeping track of requests

By: Donal Byrne - Date: March 22, 2016

At Sendify we’ve been using nats as a simple and effective means of communicating between our backend services. I came across Nats a few years ago when building a relatively small microservice backed system and it worked wonderfully. With that experience, I introduced it to Sendify this year as the main nervous system for inter-service communication. Our system is mainly processing api requests to various freight carriers based on user searches though we’re also building integration for public api access as well. Read More…

NATS and Containers: Microservices at NATS Speed

By: Brian Flannery - Date: December 11, 2015

NATS is all about simplicity and speed. In that regard, NATS is extremely well suited for microservices architectures, acting as a transport between services. Many NATS users I speak to in my role as community manager are using NATS for this purpose due to it’s lightweight PubSub characteristics. As services become increasingly distributed and modularized, an always-on, fast, PubSub communication layer becomes very important. NATS allows many distributed services and applications to function in real-time as a single entity. Read More…