3 ms·
We're using a Redis alternative called SSDB [1] in production because the entire data set doesn't need to fit in RAM. This saves us thousands of dollars per mon
by wakatime 7y ago
We're using a Redis alternative called SSDB [1] in production because the entire data set doesn't need to fit in RAM. This saves us thousands of dollars per month in server costs. Like you say, latency gains is nominal. The main reason I see alternative databases used is one missing key feature that's custom to a specific use case.
[1]: https://github.com/ideawu/ssdb https://github.com/ideawu/ssdb
- sriku 7y agoDid you test out ARDB [1] when you chose SSDB? I've been considering these for a while since I know I'm going to hit that choice point though that's not happened yet. [1] https://github.com/yinqiwen/ardb https://github.com/yinqiwen/ardb
- wakatime 7y agoLooked at it, but setup for SSDB was easier and already was using SSDB in production. Hesitant to change something that's working so well. Do have periodic connection issues with SSDB but so infrequent it's easy to work around client-side. Using the python redis [1] client with Flask. [1] https://pypi.org/project/redis/ https://pypi.org/project/redis/