MongoDB is an open source document-oriented database system. It is part of the NoSQL family of database systems. Instead of storing data in tables as is done in a "classical" relational database, MongoDB stores structured data as JSON-like documents with dynamic schemas (MongoDB calls the format BSON), making the integration of data in certain types of applications easier and faster.
$0.10
million reads
Redis Software
Score 9.1 out of 10
N/A
Redis is an open source in-memory data structure server and NoSQL database.
N/A
Microsoft SQL Server
Score 8.6 out of 10
N/A
Microsoft SQL Server is a relational database.
$1,418
Per License
Pricing
MongoDB
Redis Software
Microsoft SQL Server
Editions & Modules
Shared
$0
per month
Serverless
$0.10million reads
million reads
Dedicated
$57
per month
No answers on this topic
Subscription
$1,418.00
Per License
Enterprise
$13,748.00
Per License
Offerings
Pricing Offerings
MongoDB
Redis Software
Microsoft SQL Server
Free Trial
Yes
Yes
No
Free/Freemium Version
Yes
Yes
No
Premium Consulting/Integration Services
No
Yes
No
Entry-level Setup Fee
No setup fee
Optional
No setup fee
Additional Details
Fully managed, global cloud database on AWS, Azure, and GCP
In our early development days we weighed NoSQL databases like MongoDB with RDBMS solutions like MySQL. We were more familiar with MySQL from past experience but also were wary of painful data migrations that slowed down development iterations and increased the risk of outages …
MongoDB is our go-to database solution for any project, and the more we work with it the more we love it. Some say that NoSQL is pointless... Our developers wholeheartedly disagree, because they love working with it. Though both NoSQL and SQL have their purposes, in most …
MongoDB was the most full-featured NoSQL database we evaluated - that offered atomic transactions at a document level, built-in HA & DR, open source, robust queries, and enterprise level support.
Other platforms had specific parts of what we were looking for - MongoDB had it all.
MySQL is a great for querying related data, but it's unable to store structured data and has a fixed schema. Also SQL can be non-intuitive. DynamoDB, CouchDB and Redis all make querying the data quite difficult and lack important features. The problem CouchDB tries to solve is …
I selected MongoDB because it works for well with web interfaces. All of the RDBMS alternatives would have required a lot more time writing schemas and working around retrieving data and mapping it. That could have been somewhat mitigated with Entity Framework, but that again …
Verified User
Project Manager
Chose MongoDB
MongoDB is document oriented, and fits our goals best.
Redis Software
Verified User
Technician
Chose Redis Software
Initially, we were unsure whether to use Redis or MongoDB., in reality, they are both no-SQL databases but can be used both as needed. certainly, in my opinion, it is more reasonable a DB no SQL MongoDB than Redis, the key logic value of Redis is certainly performing for the …
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 …
Redis was initially in the list of competitors like Aerospike, Cassandra, MongoDB.The major point that outset all others is that it provides a number of read and writes to the database that no one can match. Another major factor is Redis really knows the basic components that …
Couchbase doesn't keep up with what they offer and what really does. MongoDB just doesn't scale out, reads are performed across multiple nodes but writes still go to the single master. DynamoDB is good overall but just way too expensive.
Every time you don't need a document DB, you can't go wrong with Redis over MongoDB. Google Cloud Pub/Sub may have solved one use case, but we'd still have to deploy Redis instances for other use cases, and adding another tech stack would only add complexity to our …
Redis is faster, provides documents JSON-wise with the proper odule and it is far more stable than MongoDB (we had really bad experiences with Mongo, especially when ops tends to increase).
Vice President, Chief Architect, Development Manager and Software Engineer
Chose Redis Software
All are good products. MongoDB is a great NoSQL DB but didn't seem to have the high performance caching of Redis. Coherence and Xtreme Scale are expensive. In my opinion for our particular use case, Redis was the clear winner.
Previously (not necessarily as solutions for this application stack) many have used alternatives including Memcached, MongoDB, CouchDB, Cassandra etc., and Redis was tested and compared to these other solutions - if only mentally. Ultimately while they are all good solutions …
We initially used Memcached for some of the caching and locking solutions we now use Redis for; we found that for the purposes of our system Memcache could not match up to Redis for performance. We also found Redis to be a bit more reliable, but that could have just been down …
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 …
We initially tried ElastiCache with Redis hosting. While it did the job of running Redis, we still had to deal with server sizing. We switched to Redis Cloud since that had auto-scaling and easy to use tools.
One key feature: easy to use. you can install and use it under minutes. For the rest of the options, you have to do more configuration and settings. Besides all these, Redis is in-memory so the performance is a blast. Considering that simple is better, the proof of the concept …
Redis is easy to get setup, has great documentaiton, and quality online support. Antirez is constantly making feature updates the product, and is engaged with the community. Redis doesn't have a lot of bells and whistles, but what features it does has are well implemented and …
Redis is had higher performance at a cheaper cost than any of these alternatives. The downside is the data is not as durable as these alternatives. Redis is like SQL where you pay of the instance running 24/7 where dynamo and s3 you pay per usage. Redis schema most closely …
Microsoft SQL server is easy to use and to access by everyone, (new users), can learn very easily. Most of our company uses SQL Server because it uses and joins with one of the best commands used in the industry. With MongoDB we can't use the joins so this is the plus point in …
Microsoft SQL Server is a comprehensive solution as transactional database, data warehouse, analytics, reporting, and ETL. It also integrates with the cloud well (Azure). The ease of use and setup makes this better than Oracle Database because the query syntax is also different …
Microsoft SQL Server is one of the fastest RDBMS systems available in the market. Pricing is a bit on the higher side but all the features it provides pretty much justifies it. It can be integrated with a large number of frameworks thus enabling to work on multiple frameworks …
Microsoft SQL Server is still the industry standard for the type of development we do, and the types of applications that we use. Almost every developer or analyst we hire has at least a reasonable grounding in the use of SQL servers, and it is almost universally compatible …
SQL Server is better for large databases containing structured relational data. It makes it easy to group and order, to sum and create tables of data from any data stored in a table or related tables. While Dynamodb is very good at STORING huge amounts of unstructured data, it …
SQL Server is way ahead of the support available and documentation available. Oracle should invest heavily in bringing good technical books on MySQL rather than putting documentation online and expect users to go through it.
Easy to manage all tools without extra cost is a big …
Microsoft SQL Server is more secure and offers more robustness for our data. SQL Server is also great because of its integration with Microsoft Visual Studio. It's also great because developers can build reports and stuff like that from scratch. It's faster compared to PostgreSQ…
Microsoft is more appropriate for the requirements of this particular organisation due to its ability to handle structured data efficiently and the fact that it is already widely used.
If asked by a colleague I would highly recommend MongoDB. MongoDB provides incredible flexibility and is quick and easy to set up. It also provides extensive documentation which is very useful for someone new to the tool. Though I've used it for years and still referenced the docs often. From my experience and the use cases I've worked on, I'd suggest using it anywhere that needs a fast, efficient storage space for non-relational data. If a relational database is needed then another tool would be more apt.
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.
Microsoft SQL is ubiquitous, while MySQL runs under the hood all over the place. Microsoft SQL is the platform taught in colleges and certification courses and is the one most likely to be used by businesses because it is backed by Microsoft. Its interface is friendly (well, as pleasant as SQL can be) and has been used by so many for so long that resources are freely available if you encounter any issues.
Being a JSON language optimizes the response time of a query, you can directly build a query logic from the same service
You can install a local, database-based environment rather than the non-relational real-time bases such a firebase does not allow, the local environment is paramount since you can work without relying on the internet.
Forming collections in Mango is relatively simple, you do not need to know of query to work with it, since it has a simple graphic environment that allows you to manage databases for those who are not experts in console management.
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.
An aggregate pipeline can be a bit overwhelming as a newcomer.
There's still no real concept of joins with references/foreign keys, although the aggregate framework has a feature that is close.
Database management/dev ops can still be time-consuming if rolling your own deployments. (Thankfully there are plenty of providers like Compose or even MongoDB's own Atlas that helps take care of the nitty-gritty.
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.
Microsoft SQL Server Enterprise edition has a high cost but is the only edition which supports SQL Always On Availability Groups. It would be nice to include this feature in the Standard version.
Licensing of Microsoft SQL Server is a quite complex matter, it would be good to simplify licensing in the future. For example, per core vs per user CAL licensing, as well as complex licensing scenarios in the Cloud and on Edge locations.
It would be good to include native tools for converting Oracle, DB2, Postgresql and MySQL/MariaDB databases (schema and data) for import into Microsoft SQL Server.
I am looking forward to increasing our SaaS subscriptions such that I get to experience global replica sets, working in reads from secondaries, and what not. Can't wait to be able to exploit some of the power that the "Big Boys" use MongoDB for.
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.
We understand that the Microsoft SQL Server will continue to advance, offering the same robust and reliable platform while adding new features that enable us, as a software center, to create a superior product. That provides excellent performance while reducing the hardware requirements and the total cost of ownership of our solution.
NoSQL database systems such as MongoDB lack graphical interfaces by default and therefore to improve usability it is necessary to install third-party applications to see more visually the schemas and stored documents. In addition, these tools also allow us to visualize the commands to be executed for each operation.
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.
SQL Server mostly 'just works' or generates error messages to help you sort out the trouble. You can usually count on the product to get the job done and keep an eye on your potential mistakes. Interaction with other Microsoft products makes operating as a Windows user pretty straight forward. Digging through the multitude of dialogs and wizards can be a pain, but the answer is usually there somewhere.
Finding support from local companies can be difficult. There were times when the local company could not find a solution and we reached a solution by getting support globally. If a good local company is found, it will overcome all your problems with its global support.
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.
We managed to handle most of our problems by looking into Microsoft's official documentation that has everything explained and almost every function has an example that illustrates in detail how a particular functionality works. Just like PowerShell has the ability to show you an example of how some cmdlet works, that is the case also here, and in my opinion, it is a very good practice and I like it.
While the setup and configuration of MongoDB is pretty straight forward, having a vendor that performs automatic backups and scales the cluster automatically is very convenient. If you do not have a system administrator or DBA familiar with MongoDB on hand, it's a very good idea to use a 3rd party vendor that specializes in MongoDB hosting. The value is very well worth it over hosting it yourself since the cost is often reasonable among providers.
Other than SQL taking quite a bit of time to actually install there are no problems with installation. Even on hardware that has good performance SQL can still take close to an hour to install a typical server with management and reporting services.
We have [measured] the speed in reading/write operations in high load and finally select the winner = MongoDBWe have [not] too much data but in case there will be 10 [times] more we need Cassandra. Cassandra's storage engine provides constant-time writes no matter how big your data set grows. For analytics, MongoDB provides a custom map/reduce implementation; Cassandra provides native Hadoop support.
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.
[Microsoft] SQL Server has a much better community and professional support and is overall just a more reliable system with Microsoft behind it. I've used MySQL in the past and SQL Server has just become more comfortable for me and is my go to RDBMS.
Open Source w/ reasonable support costs have a direct, positive impact on the ROI (we moved away from large, monolithic, locked in licensing models)
You do have to balance the necessary level of HA & DR with the number of servers required to scale up and scale out. Servers cost money - so DR & HR doesn't come for free (even though it's built into the architecture of MongoDB
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.
Increased accuracy - We went from multiple users having different versions of an Excel spreadsheet to a single source of truth for our reporting.
Increased Efficiency - We can now generate reports at any time from a single source rather than multiple users spending their time collating data and generating reports.
Improved Security - Enterprise level security on a dedicated server rather than financial files on multiple laptop hard drives.