Likelihood to Recommend AWS Document DB (with
MongoDB compatibility) is well suited when for all the workloads due to its huge feature offerings which will reduce our operational overhead and due to that we can focus more on our WorkLoad rather than optimising and fine tuning Databases. Its Offerings are Advanced Monitoring, DB cluster Upgrades, Migration Assistant, High Availability, Fault Tolerance, Data Durability, Security, Storage Auto Scaling, Backup Restore policies.AWS Document DB (with
MongoDB compatibility) some of the features that are there in some other services like
MongoDB Atlas that offers vast amount of features plus Supports Multi Cloud while Deploying Database clusters, Immediate support to latest Mongo DB versions, Mobile & Edge Sync like
Atlas Edge Sync, Freedom to choose Database deployment in Any top Public Cloud, Having more then 100 plus Monitoring and Telemetry metrics for index and schema recommendations, More Compatibility with
MongoDB queries.
Read full review 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.
Read full review Pros Amazon DocumentDB (with MongoDB compatibility) provides Auto scaling of cluster as a by default functionality through this we can focus on more on our applications end Through AWS Document DB without much operation overhead we can configure for Database's high availability, Durability, Backup Restores policies, Advanced Monitoring, Security Parameters. Also they can provide us a Guide for Database Migration from any Supported Mongo DB vendor to AWS Document DB. Via AWS Document DB query Logging ( Profiling ) we can fine tune our database queries and hence improving our END to END Customer Experience and Product Enhancements. Read full review 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. Read full review Cons Give support for Latest Mongo DB versions available in market AWS Document DB is limited up to 32 shards per cluster and 2 shards per Document DB instance and all within single region Start supporting more numbers of Rich data types Should have access to MongoDB experts who throw light on Cutting edge mongoDB features and integration consulting. Read full review 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. Read full review Likelihood to Renew 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.
Read full review Usability 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.
Read full review Support Rating 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.
Gene Baker Vice President, Chief Architect, Development Manager and Software Engineer
Read full review Implementation Rating Whitelisting of the AWS lambda functions.
Read full review Alternatives Considered 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.
Read full review Return on Investment Great Customer Experience as DB queries are fine tuned Less Operational Overhead to manage and take care of the Database Automatic applying of Small patches Read full review 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. Read full review ScreenShots Amazon DocumentDB (with MongoDB compatibility) Screenshots