Introducing Gloo-NATS: Bring events to your API
To be resilient, scalable, and efficient, an API Gateway should guarantee that requests are not dropped, are delivered with high performance, and can be fanned out easily to multiple subscribers. This is only possible by integrating a messaging system into the core of the gateway itself.
Until today, there were no existing gateways that leveraged a messaging system. We at Solo are excited to announce the integration of Gloo — our next-generation gateway — with the NATS messaging system. Using the power of NATS, Gloo guarantees message delivery, vastly improved performance, and buffering of messages during times of load.
NATS is an open source, lightweight, high-performance, cloud-native messaging system. It implements a highly scalable publish-subscribe (pub/sub) distribution model. The performant nature of NATS makes it an ideal base for building modern, reliable, scalable cloud native distributed systems. The CNCF recently announced that it will become the official home of the NATS project.
With this announcement we are adding another filter to enhance Envoy:
- NATS filter: Enables transforming incoming HTTP Requests into messages that are routed directly to a NATS cluster. Envoy handles the request transformation, establishing the connection, and speaking the NATS protocol, making the client completely independent from speaking the NATS API.
Gloo now provides seamless client-side integration with NATS by translating simple HTTP requests (even from a browser) to the NATS protocol, enabling persistence of requests, and high-performance asynchronous processing by connected services. Through Gloo, your HTTP requests now become events to power an event-driven architecture.
Take a look at our demos to experience the performance and scaling benefits Gloo’s NATS integration provides.