External reviews
External reviews are not included in the AWS star rating for the product.
Fast access to data
What do you like best about the product?
Simple and fast access to key/value data, as well as score and rank system.
What do you dislike about the product?
Not so easy to find/list existing keys. On the order hand, if you need list keys, probably you are doing something wrong.
What problems is the product solving and how is that benefiting you?
Cache, temporarily data, message queue, non persistent data, in memory database.
- Leave a Comment |
- Mark review as helpful
Redis - replacing AppFabric
What do you like best about the product?
Fundamentally simple enough concepts.
Lots of resources, can learn fairly the whats and hows.
Lots of resources, can learn fairly the whats and hows.
What do you dislike about the product?
no automated persistence of what gets changed in the cache
What problems is the product solving and how is that benefiting you?
Acceleration of reads for frequently-used complex data
Recommendations to others considering the product:
Usual PoC approach. Don't assume that, since it worked fine for others, it'll work for you too out of the box, even if use cases are very similar. One should learn it hands-on - no different from other critical infrastructure components.
Easy to use. But too expensive. Memory limited
What do you like best about the product?
Very easy to use. A novice can pick it up and put to use almost immediately. Documentation very easily done
What do you dislike about the product?
Very expensive, because of memory limitation. Not sure if the current version supports multiple instances
What problems is the product solving and how is that benefiting you?
I needed a database that offers very fast read and write operations. Redis delivered. Except that my needs have outgrown now
Recommendations to others considering the product:
It's really the Swiss army knife. Documentation is a breeze to pick up. Really! Performance is as advertised.
More than a database
What do you like best about the product?
Redis is easy to install, clean, nothing complex. The usage via CLI or drivers for programming languages - I wrote two for Google Go and Erlang/OTP - is simple too. But whats most fascinating is the fact, that it's not only a key/value store. The different types like hash, list, set, sorted set, hyper log log, and geo are great and useful. Also pub/sub and the internal Lua scripting help a lot. And last but not least is Redis extreme fast.
What do you dislike about the product?
The transaction model is a bit different. Users have to understand it and care for it. Additionally there's no real security model, only a simple authentication via password. There's no multi-user model and no right control regarding types, keys, or key patterns. So this has to be done by the using application while the database is secure on an internal server.
The database does not work with queries on values. Keys can be queried, other indexes have to by created by using sorted sets. But that's not the typical usage of Redis, so no larger problem.
The database does not work with queries on values. Keys can be queried, other indexes have to by created by using sorted sets. But that's not the typical usage of Redis, so no larger problem.
What problems is the product solving and how is that benefiting you?
Mostly two types of use cases. One is the typical use as a cache, simply because it's fast and the automatic key expiration (if wanted) helps a lot. The other one is the temporary aggregation of statistical data using the different data types. For some smaller projects I'm also using it as a simple data store.
Recommendations to others considering the product:
Simply try it together with the CLI and visit the web site http://redis.io to see the available commands. Most clients directly let you use these commands or provide them through own functions.
My favourite Database of Alltime
What do you like best about the product?
Its basically a datastructure store. You have a lot of data types like lists, sets, sorted sets, hash and these can directly interface with our programming languages database.
It is and in-memory database so its extremely fast and very good for high read throughput and heavy read workloads.
It is open source and free which makes it really trustworthy. It is used by us for our job server and also as a message queue and pub sub functionality for realtime notifications. Its backup and save mechanisms are really good and is easier to use than most other databases.
Its command protocol is very easy to use and implement and very fast also. Pipeling also improves threshold and is currently the fastest database I've seen.
It is and in-memory database so its extremely fast and very good for high read throughput and heavy read workloads.
It is open source and free which makes it really trustworthy. It is used by us for our job server and also as a message queue and pub sub functionality for realtime notifications. Its backup and save mechanisms are really good and is easier to use than most other databases.
Its command protocol is very easy to use and implement and very fast also. Pipeling also improves threshold and is currently the fastest database I've seen.
What do you dislike about the product?
It doesn't have truly serializable ACID transactions . Its clustering support is still not fault tolerant. It can't be used as your primary database. Doesn't have proper query language so analytics becomes a little hard and we may need to use lua for it.
What problems is the product solving and how is that benefiting you?
We bring gamification to the global mass. One importart feature for gamification is leaderboards and we use redis sorted sets a lot for it. We also use it for caching our sessions so that our users get an immediate response and we don't need to hit our databases for everything.
Recommendations to others considering the product:
If you have a lot of reads hitting your main database then you need to get redis and that stuff man.
redis review
What do you like best about the product?
Redis as a key/value network storage database gives exactly what it advertises. the In memory storage can really boost the performance of many application while relieving the developer of the headache of managing shared memory between threads or programs on the same machine or over network.
With the increasing reliability of the hardware, we are unlikely to have a server failure that will cause the loss of the data and even if that is an issue, with the persistent storage and the data replication between servers you can have a robust system that will keep your data with little to no overhead
With the increasing reliability of the hardware, we are unlikely to have a server failure that will cause the loss of the data and even if that is an issue, with the persistent storage and the data replication between servers you can have a robust system that will keep your data with little to no overhead
What do you dislike about the product?
nothing in particular, redis is a very reliable product that do one thing and do it right
What problems is the product solving and how is that benefiting you?
We started using redis as a cache system for Django, but with passing time we started using it directly in to share data between various applications and systems.
Recommendations to others considering the product:
Redis is a great tool for storing key value data, don't use it a relational database and adapt your software to redis and not the other way around to get the most of it.
Used as a cache between DB and application
What do you like best about the product?
The data structure in Redis are very helpful. The set operations helped in efficiently organizing the data and less operation needed from our end. We maintained all the Database relationship in Redis for faster access.
What do you dislike about the product?
No operation on the keys can be performed. Like sorting list based on key. There is a work around, which didn't perfectly fit well
What problems is the product solving and how is that benefiting you?
The main problem was to make the client as light as possible. Fetching data from DB was really slow for our flask application. So we thought Redis was the way to go. Where all the data are cached with drastically reduced the REST response time.
Recommendations to others considering the product:
Easily to use. Can build a prototype in a week(depends on what you want to do). Highly recommend to use
Great experience with Redis
What do you like best about the product?
Super fast response times (main purpose of redis)
What do you dislike about the product?
Data is stored in memory (needed for the quick retrieval of the data). This is generally not an issue, however very large datasets (> 250 GB) can't be fully stored in the memory and redis might not the best option for very large sets.
What problems is the product solving and how is that benefiting you?
Fast retrieval of product recommendations. Normal SQL requests take too long with larger datasets. Redis requires that the data is organized differently, but the extra work upfront pays off with every data request.
Solid product with some limitations
What do you like best about the product?
Small feature set, predictable performance, auto-expiry of data, very fast, very simple text based protocol, simple administration, easy to understand where your data is and what's happening to it.
What do you dislike about the product?
I can't say I was enormously pleased when they introduced Lua scripting. The main selling point of the data store was it's simplicity and predictable performance. It would have been preferable that a couple more commands be implemented in C rather than bring stored procedures into the mix. That choice was probably based more on product development than customer need, and again the main attraction was the premise of simplicity. In fairness, it's been a couple of years since I last used it in production so perhaps it's worked out really well since then.
What problems is the product solving and how is that benefiting you?
I've used it for auto-expiring caches, it's great for that particular use-case. Can also be used as a convenient buffer for batch processes. I wouldn't put anything into Redis that I couldn't afford to lose, I guess it's more like memcached in that respect.
Recommendations to others considering the product:
Why not give it a try? It's simple enough that you can get it running in 10 minutes. The basic commands don't take a lot longer to master, and there's some advanced stuff you can do later. I would consider it ideal for transient data storage.
showing 71 - 79