We compared MongoDB and SingleStore based on our users' reviews across four parameters. After reading all of the collected data, you can find our conclusion below.
MongoDB stands out for its flexibility, scalability, powerful query language, replication capabilities, and integration potential. SingleStore is praised for its high performance, scalability, real-time analytics, ease of use, and integration capabilities. Users of both platforms mention the need for enhancements in areas such as query execution, scalability, documentation, and user interface.
Features: MongoDB's valuable features include flexibility for working with dynamic data, scalability for large amounts of data, powerful query language, and reliable replication. SingleStore focuses on high performance, scalability, real-time analytics, seamless integration, ease of use, and intuitive interface.
Pricing and ROI: The setup cost for MongoDB is user-friendly and seamless. SingleStore is also straightforward and hassle-free. MongoDB's licensing process is described as straightforward, and SingleStore's is transparent and fair. Both products offer flexible pricing options catering to different budgets and needs. Users reported positive outcomes and benefits from adopting MongoDB. SingleStore users praised its performance, scalability, ease of use, and integration capabilities.
Room for Improvement: MongoDB users have suggested improvements to the query language, error handling, documentation, and performance optimization. SingleStore users have focused on enhancements to performance, data replication, scalability, and ease of use.
Deployment and customer support: The initial setup of MongoDB is straightforward, especially for those with prior experience in databases. It can be deployed in a couple of hours or even less, either on-premises or on the cloud. Some mention that cluster deployment can be a bit more complex and may take a couple of days. The availability of community support and the ease of learning the initial setup process makes it accessible to users without prior experience with MongoDB or traditional SQL databases. The duration required for deployment of SingleStore can vary depending on the experience of the person performing it. Cloud installations are simple and can be done by anyone (even someone less technical) in a matter of hours by following the provided instructions. Bare-metal installations might take a day for a new technical person, however, an experienced one can do it in an hour. MongoDB's customer service is consistently praised for exceptional assistance, responsiveness, and expertise. Users highlight prompt issue resolution, knowledgeable support staff, and effective communication. SingleStore customers express satisfaction with prompt and helpful assistance, knowledgeable staff, and responsive services.
The summary above is based on two interviews we conducted with MongoDB and SingleStore users. To access the review's full transcripts, download our report.
"It is easy to set up."
"It's super easy to develop a couple of solutions for clients with MongoDB, like a quick web page with no clear data structure that they need to spin up quickly to validate some sort of MDTP."
"It can handle a lot of files quickly."
"The installation is very stable."
"The most valuable feature of MongoDB is the NoSQL database. In a SQL database, we need to join data together with a unique ID amongst other things, but in MongoDB, it's not required. We can directly receive all the information. The performance is very good. Additionally, they have frequent updates."
"We haven't had any issues with stability."
"The most valuable feature is that you can store unstructured data, which is helpful when you don't know what the best structure should be and you cannot use a relational database because of that."
"It is very fast - faster than an SQL or MySQL Server."
"The paramount advantage is the exceptional speed."
"The ability to store data in memory is a standout feature, enhanced by robust failover mechanisms."
"MemSQL supports the MySQL protocol, and many functions are similar, so the learning curve is very short."
"The product's initial setup phase was pretty straightforward, with no complex processes."
"It's a distributed relational database, so it does not have a single server, it has multiple servers. Its architecture itself is fast because it has multiple nodes to distribute the workload and process large amounts of data."
"The most valuable feature is the ability to create pipelines, streamline and extract data from the pipelines."
"The product can automatically reinstall and reconfigure in case of a shutdown."
"The solution can be a bit tough to set up if you don't have knowledge about how the database works."
"People coming from RDBMS should have the flexibility to write queries in SQL that can be converted into JSON queries."
"It could be more stable. It would be better if it were more user-friendly like Oracle, which is very easy. For example, creating an index is simple in Oracle. In MongoDB, it's quite challenging to do that. Performance could be better. It's fast and good, but you cannot put every application that you would like to in MongoDB."
"The on-premises version of the solution is still pretty expensive, especially compared to the cloud version."
"I have found the solution difficult to operate as an administrator."
"MongoDB could improve by not having so many updates and different versions."
"I'd like to see an ID generator. It's very technical but I don't think it has one, so we have to go to great lengths to work around that."
"The solution should have better integration."
"We don't get good discounts in Pakistan."
"The product can be developed further to provide more appropriate output to users as it is one of the areas where there are shortcomings."
"Poor key distribution can significantly impact performance, requiring a backward approach in design rather than adding tables incrementally."
"Having the ability to migrate servers using a single command would be extremely beneficial."
"For new customers, it's very tough to start. Their documentation isn't organized, and there's no online training available. SingleStore is working on it, but that's a major drawback."
"It is not the optimal choice for direct data collection through queries, and it's more suited for aggregation tasks."
"There should be more pipelines available because I think that if MemSQL can connect to other services, that would be great."
MongoDB is ranked 1st in NoSQL Databases with 70 reviews while SingleStore is ranked 6th in Database as a Service with 7 reviews. MongoDB is rated 8.2, while SingleStore is rated 8.8. The top reviewer of MongoDB writes "Lightweight with good flexibility and very fast performance for searching data". On the other hand, the top reviewer of SingleStore writes "A reasonably priced product that offers good speed and seamless support". MongoDB is most compared with InfluxDB, Couchbase, ScyllaDB, Cassandra and Oracle NoSQL, whereas SingleStore is most compared with SQL Server, MySQL, Teradata, CockroachDB and InfluxDB.
We monitor all NoSQL Databases reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
SQreamDB is a GPU DB. It is not suitable for real-time oltp of course.
Cassandra is best suited for OLTP database use cases, when you need a scalable database (instead of SQL server, Postgres)
SQream is a GPU database suited for OLAP purposes. It's the best suite for a very large data warehouse, very large queries needed mass parallel activity since GPU is great in massive parallel workload.
Also, SQream is quite cheap since we need only one server with a GPU card, the best GPU card the better since we will have more CPU activity. It's only for a very big data warehouse, not for small ones.
Your best DB for 40+ TB is Apache Spark, Drill and the Hadoop stack, in the cloud.
Use the public cloud provider's elastic store (S3, Azure BLOB, google drive) and then stand up Apache Spark on a cluster sized to run your queries within 20 minutes. Based on my experience (Azure BLOB store, Databricks, PySpark) you may need around 500 32GB nodes for reading 40 TB of data.
Costs can be contained by running your own clusters but Databricks manage clusters for you.
I would recommend optimizing your 40TB data store into the Databricks delta format after an initial parse.
Morten, the most popular comparisons of SQream can be found here: www.itcentralstation.com
The top ones include Cassandra, MemSQL, MongoDB, and Vertica.