What is the logic behind separating those from the core server? Binary size? Automatic configuration? "Wow this has a lot of features" vs "wow what are all these extra things I need to sift through to figure out what I need", no?
Redis Stack
31–40 of 71 posts
Re: Redis Stack
#32Re: Redis Stack
#33Re: Redis Stack
#34I don't understand why there is timeseries solution there, usually people who use timeseries work with many Gigas of storage, are we gonna pay for RAM to do that?
Second, many Gigas is what you get from any small size server... And, on top of that Redis/TimeSeries supports an almost linear scale out which allows your memory to increase dynamically according to your needs. Last, Redis Enterprise (& Cloud) add Redis on Flash support extending your RAM to your local Flash storage.
Re: Redis Stack
#35I want to do a sentiment analysis on Redis-related HN comments pre and post antirez departure.
Re: Redis Stack
#36Is this something Redis are likely to offer in future does anyone know?
Re: Redis Stack
#37Around two months ago I was excited to learn about RedisJSON, only to get to know that there is no ARM-based Docker image available for installing it on a Raspberry Pi.
Re: Redis Stack
#38It would be great if ElastCache supports this
Re: Redis Stack
#39It’s a shame they don’t offer first class Ruby support. I could see myself using some this stuff. Is this something Redis are likely to offer in future does anyone know?
It's a datastore. It has clients for many languages, including a recommended one for Ruby. What support are you missing here?
Re: Redis Stack
#40It’s a shame they don’t offer first class Ruby support. I could see myself using some this stuff. Is this something Redis are likely to offer in future does anyone know?
e.g.
* https://github.com/npezza93/redi_search
* https://github.com/vachhanihpavan/rejson-rb
* https://github.com/dzunk/redis-time-series
You can see on each modules docs the list of clients developed by the community. e.g.