TrustRadius
Redis is an open source in-memory data structure server and NoSQL database.https://dudodiprj2sv7.cloudfront.net/product-logos/jG/Kt/P5M6TS4T2XVL.pngRedis LabsRedis - memory is the new disk2018-03-30T20:49:06.006ZI used Redis in the context of an Airline company middleware implementation. At that time, we were looking for an efficient caching solution with the possibility to distribute data across nodes (i.e. sort of data grid without the complexity of a data grid).
Redis allowed us to build very fast a small cluster of nodes (4) serving as a cache for storing web sessions.
Because of additional features of Redis (pub/sub, in memory Keystore), Redis was also identified as non-critical storage for some data.,Redis is easy to learn and concepts are very simple. It's an in-memory storage with regular snapshots for data resiliency.
Redis offers the possibility to act as a cache with limited but strong eviction set policies. LRU is the most common one.
The pub/sub feature of Redis is an interesting alternative for efficient and fast data distribution when we don't need a central broker such as JMS. Obviously, it requires some analysis before choosing between the bunch of providers (JMS, Kafka, MQTT, AMQP, Redis, etc),Redis is sponsored by Redislab which limit its functionalities. This is normal but they should push for a graphical tool for Redis monitoring. This tool is available for the enterprise edition, it would be nice to have a core version for the community
I don't know if Redis is available in containers, this might be interesting to have such capability,8,Redis has a fast learning curve for developers and operations teams.
Community edition allows touching a small part of Redis capabilities. In case we need support and additional features, we can decide to buy the enterprise edition which offers many additional features.,Hazelcast, memcached and TIBCO ActiveSpaces,Vagrant, Docker, OpenShift,9,15,5,The main use case was for caching data in a distributed context. Redis is really powerful while dealing with data sharding and heavy traffic load
Another use case of Redis was the capacity to server faster data compare to physical databases. It was used for non-critical systems.
The last use case (minor) was to explore the pub/sub capability of Redis in the context of the multi-tenant application,To be honest, we were not really innovating with Redis, we were using common features.,I'm not anymore working for the company, but I remember that LUA script was explored. They were also trying to build bigger cluster (~100/150 nodes)Hugo Romani CortesRedis on high scalability world2018-01-31T16:10:02.761ZWe use redis and recommend for our clients. The key areas Redis outsteps all others are:
1) Scalability
2) Unique and flexible key value db structure
3) They use Ssd Flash for their instances
They also provide session management capabilities to be implemented in any huge projects without much headache. Their db instance also provides a high number of read write per second, which makes it a leader.,Session Management
Key value pair DB structure
High scalability
Flash instances,Failover Replicas
Data Consistency,I will be delighted to answer this particular question. Redis has a unique geo spatial records handling product that makes me sort millions of records according to user location, that may vary from user to user. This helped me to scale the speed of 3 minutes to just 20 seconds when combined with google cloud capabilities.,10,It increased my speed of meshing.
It increased my user experience by stream-less rendering.
It created huge impact in my metasearch, my basic income has increased by 120% in last 45 days.,Cassandra, MongoDB and Aerospike Database,Google Cloud SQL,10prakash psTrust Redis: A Review on TrustRadius2018-03-16T19:47:11.140ZRedis was used internally by software development teams as part of a web application stack. Each development team was free to use alternate technologies, including none at all, but for teams with performance requirements, Redis was chosen to provide an in memory cache layer buffering web requests from directly hitting the database.,In memory caching
Fast read and write access
Data structure based API,Clustering and sharding
Self managing for high availability
Failover,Redis' in memory implementation makes it particularly well suited as an application cache. For Web tier stacks, it can be used for session management. In addition to its in memory implementation, its core API is based around data structures, not just Key-Value Pairs, making it far more versatile for caching database responses.,9,Redis has reduced the hardware requirement cost for our RDMS machines, by offloading work to redis servers
There is increased complexity which translates to development time, in order to build an application to leverage Redis
The increased complexity in application design has a net benefit of increasing fault tolerance,Memcached and MongoDB,Evernote, G Suite, Stripe,9Verified UserA good key-value\no SQL product2018-02-06T17:39:50.840ZWe have tried using Redis to move from a relational DB to a key-value logic. In view of the use of a DB not SQL, it is certainly performant even if unlike other SQLs, it requires a little more reasoning about the proper analysis of the key value to be used and the way in which they are then interrogated.,key - value logic
no SQL structure
really speedy queries,need an initial implementation
without a correct key - value queries do not perform
need a change of the actual application to move from SQL to Redis,Redis is definitely a good solution (in the best case) if you are willing to change your SQL structure to a no-SQL structure, but only if you know what you want to get and what kind of application you want to access the data, otherwise the performance can be very degraded.,8,SQL server freed from workload
less effort to clean up unnecessary data,MongoDB,8Verified UserRedis: Awesome in-memory key-value distributed CAP compliant store2017-10-09T20:00:11.057ZWe use Redis for low latency repetitive point queries. To break it down:
Low latency: As it is in memory, saves on I/ORepetitive: As part of ETL we use it to address resolution, .i.e. given an address, find a representative lat long for it. As millions of rows are ETLed every day, there is high chance that they repeat. Having in-memory helps againPoint queries: WHERE age BETWEEN 10 and 30 is a range query and WHERE age = 15 is a point query. We use it only for point queries,When dataset is small enough to fit in-memory and get full benefits of reduced I/O
Need of rich data structures for complex querying
Speed of in-memory store and durability by disk at the same time,Declarative querying like SQL
Tools for monitoring and identifying performance bottlenecks
Key schema design can be tricky and heavily impacts the performance (leading to key scans),Redis ModulesAbility to extend Redis is a huge power using its robust backend pipelineRedis Enterprise has smart support for FlashRedis (e) smartly decides, based on usage, which keys to put in RAM and what to put in SSD, opening up whole new possibilities of storing more data and not needing to create subsets for RedisOptimistic concurrency control support
An educated developer knows better on what objects to obtain lock and avoid concurrency and dead lock problems which other databases run into. Redis gives the flexibility to either create a critical section or obtain optimistic locks on certain variables,10,We use it all the time for point queries and it worked well
Though it is in-memory it is distributed and durable
We need high availability for ETL and low read latency accelerates even further,MemSQL,React,10Nitin Pasumarthy
Unspecified
Redis
54 Ratings
