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

In this, the 3rd part of Dale Bingham’s series on “Using NATS to Implement Service Mesh Functionality”, Dale speaks about how to have similar service mesh benefits, usage and design when using the NATS messaging system as your communication backbone. As with anything dealing with software engineering, there are pros and cons to deciding on languages, infrastructure, and design models. It is always great to have alternatives and new ways of looking to solve problems.

This third article goes over the observability piece, or at least part of observability. We will see how the metrics, tracing, and alerting are done with respect to NATS in comparison to the similar functions you get with the major service meshes.

Read the full article Using NATS to Implement Service Mesh Functionality Part 3: Metrics, Tracing, Alerts, and Observability.

service mesh nats

More About the Author

Dale Bingham is the CTO of Cingulara. Software Geek by trade. Father of three daughters. Husband. Lover of newer tech where it fits. Follow at @cingulara

Back to Blog