You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
ServiceStack.Redis is only free up to a limited number of API calls per hour, after that it is a paid product. We use ServiceStack.Redis because our implementation of queues over Redis requires use of a Blocking Pop operation which cannot work on a multi-plexed channel over a single threaded database like Redis. This creates an issue for high-volume users, they are forced to pay for ServiceStack
Describe the solution you'd like
Since we wrote our Redis support, Redis has released support for Streams. Streams are a more natural building point for queues than the list based solution we have used up to now. If we switch to streams we can also switch the client to StackExchange.Redis, which is free.
Describe alternatives you've considered
We could drop back to using an earlier version of ServiceStack, before it became a paid for product, but this exposes us to a range of new issues.
Additional context
None
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
ServiceStack.Redis is only free up to a limited number of API calls per hour, after that it is a paid product. We use ServiceStack.Redis because our implementation of queues over Redis requires use of a Blocking Pop operation which cannot work on a multi-plexed channel over a single threaded database like Redis. This creates an issue for high-volume users, they are forced to pay for ServiceStack
Describe the solution you'd like
Since we wrote our Redis support, Redis has released support for Streams. Streams are a more natural building point for queues than the list based solution we have used up to now. If we switch to streams we can also switch the client to StackExchange.Redis, which is free.
Describe alternatives you've considered
We could drop back to using an earlier version of ServiceStack, before it became a paid for product, but this exposes us to a range of new issues.
Additional context
None
The text was updated successfully, but these errors were encountered: