Building a Microservices Control Plane using NATS and Docker Engine v1.12

By: Wally Quevedo - Date: August 22, 2016

For those of you who might have read the previous post I did on Docker + NATS for Microservices, you’ll recall we took an in-depth look at using Docker Compose with NATS. That blog post was done a few days prior to DockerCon, and as expected Docker made many interesting announcements at DockerCon. One of the main things announced that week was Docker 1.12. 1.12 includes Swarm mode which can be used for assembling a cluster of Docker Engines and running workloads on them. Read More…


Guest Post: How Ariane is moving from monolith to microservices with NATS

By: Mathilde Ffrench - Date: August 16, 2016

Some words about the Ariane project: While the DevOps trend is reducing application delivery time with automation on any step of the deployment, we still need to reduce the time to understand complex distributed applications: We still rely on hand-written technical documentations and diagrams; These documentations and diagrams are dispatched across teams (silo effect); The documentations and diagrams are also often not up to date (technical debt effect). Knowledge management is a key factor in reducing silo effect and improving the integration of new team members. Read More…


Docker Compose + NATS: Microservices Development Made Easy

By: Wally Quevedo - Date: June 20, 2016

Buzzwords are everywhere in our industry. “Microservices”, “Serverless computing”, “Nanoservices”, “Containerized” - you could fill a whole blog post just with these overused phrases. If you cut through the terminology flavor of the month, there are some very important common thread for application developers. One is simplicity. Regardless of what architectural approach you’re using - and what you may or may not refer to it as - you want it just work. 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…