Microservices rely on interservice communication to share events, state, and data as well as to maintain isolation and decoupling. Many developers implement an asynchronous event-driven publish-subscribe message broker for interservice communication, but doing so is complicated.
Here’s a better way: Redis Streams acts as both a native log data structure and communication channel that can publish an event without requiring an immediate response. It is simple to deploy, supports message persistence, and offers scalability through consumer groups.
|The microservices problem
|The Redis Enterprise solution
|It’s hard to keep microservices isolated, and, at the same time, communicate state, events, and data
| Redis Streams is a lightweight asynchronous message broker that is both an immutable time-ordered log data structure and event store.
Redis is simple to deploy with out-of-the-box partitioning, replication, persistence, and configurable message delivery guarantees.
|Scaling and maintaining microservice communications is difficult, especially during traffic spikes
| Redis Streams provides efficient write/read operations to improve overall application performance
It can capture and process millions of data points per second at sub-millisecond latency
It includes advanced consumer group functionality that enables you to split a stream of messages among multiple clients to speed up processing.
|Complexity and development cost of using Kafka as message broker
| Redis Streams’ lightweight implementation requires only a key-value pair. That’s far simpler than the administrative overhead of setting up a Kafka topic.
Redis Enterprise Operator for Kubernetes enables automated Redis Enterprise cluster deployments.
Redis Streams and caching are on one unified multi-tenant data platform. No additional license is required.