-
Notifications
You must be signed in to change notification settings - Fork 113
Redis Streams support #34
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
Comments
No current plans. Would you personally use Redka in this use case? |
Yes, definitely. Support for full streams API would allow me to switch from Kafka to Redka Streams for dev/ci/testing environments. Using Redis Streams currently doesn't have much sense to me, because of high requirements for a memory which is way more expensive than disk in a cloud. My use cases usually require long data retention but are fine with reduced performance. |
If you only use Kafka in production (and Redis/Redka in dev/test), doesn't that mean that Kafka-related features don't get tested at all? Is that wise? |
I'm using te same protocol on all environments. Currently it's Kafka. |
I see, thanks for the explanation! I will look into streams after the 1.0 release. I'll leave the issue open to see if anyone else is interested in this feature. |
Are there a plans to implement streams?
Redka Streams would be perfect replacement for Redis Streams in many Kafka use cases where disk storage is required and/or memory is restricted.
The text was updated successfully, but these errors were encountered: