-
-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add redis-streams backend #115
Add redis-streams backend #115
Conversation
5eb090a
to
9f0a84b
Compare
README.md
Outdated
@@ -111,6 +112,6 @@ state, make sure to strictly pin your requirements to `broadcaster==0.2.0`. | |||
To be more capable we'd really want to add some additional backends, provide API support for reading recent event history from persistent stores, and provide a serialization/deserialization API... | |||
|
|||
* Serialization / deserialization to support broadcasting structured data. | |||
* Backends for Redis Streams, Apache Kafka, and RabbitMQ. | |||
* Backends for Apache Kafka, and RabbitMQ. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is What's next
section. Redis Streams lands with this PR and Kafka is already there.
Are you able to give a brief pointer towards when there'd be a use-case for redis streams vs. redis pub/sub? (Just in this conversation is enough, I don't think we have sufficient docs to have a good place for this right now) |
Redis Streams is a lightweight Kafka alternative. While pub sub is fire-and-forget, Redis stream is an append only log. |
Reviews README and discovers that past me already wrote about this. Thanks that person.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍🏼
thanks 🙏 |
Based on #102
Seems that the author of #102 did not notice a call for update, so I am creating a new PR in order to proceed with this backend.
@encode/maintainers please do a review
closes #102
closes #3