Redis is great at set operations and is very fast. Riak is a fast long-term data store, but it is expensive to run. MongoDB is good for small, quick projects. Elasticsearch is great at indexing and searching. Choose the right tool for the job, and don't be afraid to …
Every database has positives and negatives. Redis is very good at set operations, but not as good at executing fast queries. MongoDB is a much cheaper data store than Riak, but not as highly available and scalable. Searching Riak is also faster than searching MongoDB or Redis…
Because of the RESTful HTTP interface, the consistency model, and because of the catalog-driven data model, Riak was an easy win over Redis and Memcached.
At the time I worked on the project those were the three competing technologies I evaluated. Couchbase didn't have memcache integrated at the time. Riak was by far the easiest to set up, and it's linking capability struck the right balance of having just enough relational …
IBM Informix creates an effective and secure channel for easy and quick data management and transfer across other major Cloud platforms and other data storage systems. The analytical ability is also the best and most effective visual functionalities and the encryption and the data archiving functionalities are great and easy on reporting.
Redis has been a great investment for our organization as we needed a solution for high speed data caching. The ramp up and integration was quite easy. Redis handles automatic failover internally, so no crashes provides high availability. On the fly scaling scale to more/less cores and memory as and when needed.
Excellent Data Warehouse performance from the basic engine. Outstanding Data Warehouse performance from the Informix Warehouse Accelerator module.
Best embedability among major RDBMS systems.
Scalable from the smallest Raspberry PI up to the largest monolithic systems and out to dozens of distributed nodes.
Hybrid data capabilities to merge relational data with time seriesv, geospacial data, JSON data and other non-traditional data types with performance comparable or better than systems dedicated to those data types.
Easy for developers to understand. Unlike Riak, which I've used in the past, it's fast without having to worry about eventual consistency.
Reliable. With a proper multi-node configuration, it can handle failover instantly.
Configurable. We primarily still use Memcache for caching but one of the teams uses Redis for both long-term storage and temporary expiry keys without taking on another external dependency.
Fast. We process tens of thousands of RPS and it doesn't skip a beat.
Highly available: If nodes go offline for any reason, the system still operates.
Highly scalable: There is a minimum of 5 nodes, which can handle a lot by themselves. When scaling is required, it can be done easily, with minimal to no downtime on large scales.
Very fast searching: Riak has SOLR indexing built-into the core product, which makes querying for data very fast.
It is very difficult to find a missing functionality in Informix, technically is great. I will again criticize the business side and how it has been managed over the past, I hope this could be improved with HCL's help. I know they are working hard, but we need to start letting the world know and revert their concept about its existence and that it is one of the best competitors within the data treatment, in the market. We need to start telling the world about success cases and stories showing this and backing up its strong technology.
We had some difficulty scaling Redis without it becoming prohibitively expensive.
Redis has very simple search capabilities, which means its not suitable for all use cases.
Redis doesn't have good native support for storing data in object form and many libraries built over it return data as a string, meaning you need build your own serialization layer over it.
Deletes!!! We've seen on numerous occasions where Riak has "resurrected" deleted data. We've worked with Basho numerous times and tried multiple changes to the way we interact with Riak to prevent the problem but it still remains. The deletes seem to reappear weeks, even months, after the delete was issued. We've had to work around this issue by providing a "deleted" flag for all data objects stored in Riak. Thus, we do no delete but simply flip the flag. Excess baggage we would really like to not have to worry about.
Search. Currently there's no way to tell what data you have in Riak without already knowing a particular bucket/key. There is a way to list the keys for a given bucket but due to performance implications, this is not a viable method to lookup data. Especially when you have a large amount of keys in the bucket.
We will definitely continue using Redis because: 1. It is free and open source. 2. We already use it in so many applications, it will be hard for us to let go. 3. There isn't another competitive product that we know of that gives a better performance. 4. We never had any major issues with Redis, so no point turning our backs.
Right now, I'm on a project where we need databases that can run on embedded systems. Riak isn't necessarily the best fit for that scenario. But when we need a clustered database, that's where we'd start considering Riak.
It is quite simple to set up for the purpose of managing user sessions in the backend. It can be easily integrated with other products or technologies, such as Spring in Java. If you need to actually display the data stored in Redis in your application this is a bit difficult to understand initially but is possible.
The support team has always been excellent in handling our mostly questions, rarely problems. They are responsive, find the solution and get us moving forward again. I have never had to escalate a case with them. They have always solved our problems in a very timely manner. I highly commend the support team.
Despite Basho going bankrupt and the project becoming fully open-source, community support is reasonably good, albeit a little slow at times. Paid enterprise-grade support is also available from former Basho engineers but the same company also contributes to the community support for free for basic questions or specific knowledge areas.
IBM Informix creates effective solutions for big data extraction and data transportation functionalities across the entire Cloud services and the Automation ability is the best. The security that IBM Informix provides for all our business data and other project information and contacts is effective and the reports are very clean and easy to understand.
We are big users of MySQL and PostgreSQL. We were looking at replacing our aging web page caching technology and found that we could do it in SQL, but there was a NoSQL movement happening at the time. We dabbled a bit in the NoSQL scene just to get an idea of what it was about and whether it was for us. We tried a bunch, but I can only seem to remember Mongo and Couch. Mongo had big issues early on that drove us to Redis and we couldn't quite figure out how to deploy couch.
Because of the RESTful HTTP interface, the consistency model, and because of the catalog-driven data model, Riak was an easy win over Redis and Memcached.
Although I do not own nor have visibility on my company's figures:
Informix generates consistent savings on DBA staffing, no need for many DBAs as other DBMS require.
The replication architecture allowed consistent savings in the infrastructure as well as developments and maintenance, the job is already done, no need to develop complex and costly solutions, it's just a matter of configuring it.
The advantages of hybrid development (i.e mixing SQL and NoSQL in the same database) is not just a marketing hype: it allowed us to solve with a brilliant solution, in one afternoon of coding, a functional problem we have been having for more than 10 years!
The biggest drawback is that IBM pricing may be constraining, it has too important gaps between the mid range and highrange in terms of pricing
Redis has helped us increase our throughput and server data to a growing amount of traffic while keeping our app fast. We couldn't have grown without the ability to easily cache data that Redis provides.
Redis has helped us decrease the load on our database. By being able to scale up and cache important data, we reduce the load on our database reducing costs and infra issues.
Running a Redis node on something like AWS can be costly, but it is often a requirement for scaling a company. If you need data quickly and your business is already a positive ROI, Redis is worth the investment.
Riak has been a key part of our company's build process for our client's search backend. It is valuable for is in that it provides a reliable way to view the current search index.
