2 Reviews and Ratings
224 Reviews and Ratings
For running application tests it's well suited. H2 [Database Engine] can replace the real-world database solution for them easily and removes the requirement to set up a a separate database instance just for running unit tests. For using in actual production application one needs to consider scale. H2 is suitable if application runs in single instance and database is located in same machine as a file where that application runs. This means the application shouldn't have a large user base. However it's easy to switch to an actual MySQL instance if the need arises, it's most likely only a configuration change and doesn't require new code.Incentivized
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.Incentivized
Can run as an in-memory database.Simple and quick to get started with, and is light weight (only 2MB).SQL compliant so it compatible with most relational databases.Incentivized
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.Incentivized
There's a warning in official FAQ "Is it Reliable?"-section which makes it seem like H2 is not yet a mature product.If raw SQL queries are used there maybe be differences between MySQL & H2. ORM library should be used.Support seems to be community-based only.Incentivized
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.Incentivized
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.Incentivized
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.Incentivized
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.Incentivized
Whitelisting of the AWS lambda functions.Incentivized
While both can run as an in-memory database, H2 Database Engine was just so much easier for us to use since we primarily use the Java stack and H2 Database Engine is also built with Java.Incentivized
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.Incentivized
Doesn't take time from developers, once it's configs are set up for testing it works in everyone's development environmentsEasy to integrate in application, no need to setup separate database software, no maintenanceNo need to deal with infrastructure related issues/costs - database runs in same machine as the application that uses it.Incentivized
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.Incentivized