We use this solution for database verification purposes. Typically, we integrate other analytics tools with the solution, like databases and other tools.
MongoDB
ATH InfosystemsExternal reviews
17 reviews
from
External reviews are not included in the AWS star rating for the product.
The Dynamic Application feature is very valuable and the solution's setup is straightforward
What is our primary use case?
What is most valuable?
The Dynamic Application is a valuable feature.
What needs improvement?
The analytics needs improvement.
For how long have I used the solution?
I have been using MongoDB for a couple of years.
What do I think about the scalability of the solution?
Hundreds of users use the solution at present.
How was the initial setup?
The initial setup is straightforward.
What other advice do I have?
Overall, I would rate the solution an eight out of ten.
Provides ease of integration and simpler configuration process
What is our primary use case?
We use MongoDB mainly for data visualization and filtering purposes.
What is most valuable?
MongoDB's most valuable feature is data visualization.
What needs improvement?
They could provide more documentation and examples for adding pipeline stages. There could be a feature where commands made in MongoDB could be easily copied and shared in their original format. This functionality would enable seamless transition and compatibility between platforms like Linux and mobile devices, reducing the need for complex filters or Citrix-based solutions.
For how long have I used the solution?
We have been using MongoDB for five months.
What do I think about the stability of the solution?
I rate the platform's stability a nine out of ten.
What do I think about the scalability of the solution?
My department has around 50 MongoDB users.
How was the initial setup?
It is a cloud-based version and is simple to deploy.
Which other solutions did I evaluate?
We evaluated OracleDB and MongoDB. We decided to work with MongoDB as its interface is easier to understand and more universal. It offers ease of integration and simpler configurations compared to OracleDB. It also provides all the essential functionality.
What other advice do I have?
I rate MongoDB a nine out of ten.
A tool that offers good integration capabilities
What is our primary use case?
I use MongoDB in our company since our overall data is stored on it. My company uses the tool as a back-end database.
What is most valuable?
The most valuable features of the solution are that it appeases our company's needs and is quick.
What needs improvement?
The dashboard is an area of concern in the solution where improvements are required. The price of the product may be a concern for the customers who use it, so improvements may be required in the pricing model.
For how long have I used the solution?
I have been using MongoDB for more than ten years. I use the solution's latest version.
What do I think about the stability of the solution?
Stability-wise, I rate the solution an eight out of ten.
What do I think about the scalability of the solution?
Scalability-wise, I rate the solution a seven out of ten.
It is always important to ensure that users use the latest version of MongoDB if they want to use the scalability features of the product.
There are more than 1,000 users of the solution.
My company plans to expand the number of users of the product.
How are customer service and support?
MongoDB's technical support team is responsive and helpful.
I rate the technical support an eight out of ten.
How would you rate customer service and support?
Positive
How was the initial setup?
The product's initial setup phase was quite easy, but for some use cases, it was a bit difficult.
The solution is deployed on the private cloud services offered by AWS.
The solution can be deployed in a couple of hours. The product's initial deployment phase can be taken care of in an hour, and if any further deployments are required after that, it takes less than an hour.
Six to seven engineers are required to take care of the deployment and maintenance phases of the solution.
What other advice do I have?
The integration capabilities of MongoDB are fine for the solutions that we use in our company.
The tool's vendor takes care of the product's maintenance.
I rate the overall solution an eight out of ten.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Enhanced flexibility in data modeling, seamless scalability and efficient handling of unstructured or complex data through its document-oriented structure
What is our primary use case?
The primary use case is data retrieval. It allows for easy retrieval of data as all the required information is stored within the document. This becomes particularly useful as the company scales, preventing queries from becoming sluggish.
How has it helped my organization?
Working with it extends beyond database skills. Utilizing additional tools such as ML frameworks (e.g., TensorFlow), languages like Python for data analysis, and platforms like Apache Spark for distributed computing can enhance one's capabilities in extracting meaningful insights from data.
What is most valuable?
It facilitates the generation of heatmaps for graphical data analysis. This can be valuable for visualizing patterns and trends in data. While other databases like Cassandra may also serve this purpose, MongoDB stands out for its simplicity in handling complex queries and graphical data representation.
What needs improvement?
It has certain limitations when it comes to handling hierarchical data, enforcing relationships, and performing complex joins, which should be taken into account when designing databases for applications with intricate data requirements.
For how long have I used the solution?
I have been working with it for a year now.
What do I think about the stability of the solution?
It is highly stable. I would rate it nine out of ten.
What do I think about the scalability of the solution?
It emerges as a favorable choice for customers seeking efficient data storage and scalability. On a scale of one to ten, I would rate it at eight.
Which solution did I use previously and why did I switch?
I have been working with both MongoDB and HIVE and the choice between them depends on the specific requirements of the client. While I've been actively engaged with both databases, the preference depends on the nature of the data and whether file storage is required. If data retrieval is the primary focus without the need for file storage, I opt for MongoDB. On the other hand, if the client requires storage for both data and files, HIVE becomes the main choice.
How was the initial setup?
I would rate the initial setup six out of ten.
What's my experience with pricing, setup cost, and licensing?
I only used the open-source version.
What other advice do I have?
Opting for MongoDB could be beneficial, especially for storing large volumes of records, even for transient data. The decision hinges on the nature of the data itself. If there is a significant amount of metadata, it becomes a preferable choice for its scalability and superior query performance. It's important to anticipate future operations; for example, if there's a current load of ten thousand audio and video files, MongoDB can efficiently handle it. Overall, I wold rate it eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
A stable solution that can be used to store structured, unstructured, and semi-structured data
What is most valuable?
Sharding is an excellent feature of MongoDB. Atlas is an awesome feature of MongoDB that makes life easy.
What needs improvement?
People coming from RDBMS should have the flexibility to write queries in SQL that can be converted into JSON queries. This feature is working, but we can still achieve some integration and make it more flexible. It is not as easy as writing direct queries on Atlas. This feature will definitely increase a lot of users. RDBMS users think this is a different query language, MQL, which is uncomfortable for them.
For how long have I used the solution?
I have been using MongoDB version 6.0 for more than 12 years as a customer.
What do I think about the stability of the solution?
MongoDB is a very stable solution. The solution is a leader, according to the Gartner report.
What do I think about the scalability of the solution?
In our company, around 2000 to 3000 people are using the solution.
How are customer service and support?
MongoDB’s technical support is awesome.
Which solution did I use previously and why did I switch?
How was the initial setup?
It is very easy to deploy MongoDB. If it is deployed on-premises, it takes an hour. It does not need any additional prerequisites or configuration details.
What was our ROI?
We have seen a lot of ROI with MongoDB because it gives five to ten times better performance.
What's my experience with pricing, setup cost, and licensing?
MongoDB's pricing is not reasonable, but it is not as expensive as the others.
The solution's pricing depends on the deal, which includes how long you will use it and the number of deployments. They do not have a fixed cost. However, the maintenance and support cost is included.
What other advice do I have?
I am satisfied with the product.
Our organization has a DBA team of 50 people. However, the work for the DBAs is minimal because MongoDB intends to have zero DBA. They want to develop a product where the need for DBAs is minimized.
Users should approach MongoDB with an open mind, without thinking that it's a different technology altogether and has a different language. Users don't need to develop the application based on a schema. They can develop the application, and the schema will follow.
Overall, I rate MongoDB an eight out of ten.
A solution that is affordable and high on performance
What is our primary use case?
I work with multiple personal applications, and for that, I use MongoDB and SQL Servers. Depending on the use cases, I choose MongoDB, as it is not a heavy application. Usually, I use MongoDB for attachment sections because RDBMS is heavy for attachment software. I also use it for assessments. Sometimes, I store data for a time-series database, such as stock market data, which I analyze using MongoDB.
What is most valuable?
Feature-wise, I like how MongoDB stores attachments because it allows me to store the results of the attachment and pull them up whenever needed instead of having to generate them every time. I can save those results as PDFs and other formats rather than just saving the data and then having to regenerate it. This approach enables me to analyze the attachments and research existing data, making it easier to retrieve information when needed. Overall, MongoDB has helped manage and analyze attachment data.
What needs improvement?
I cannot comment on how to improve the database since I am not an expert in that field. It is important to note that MongoDB has limitations since it can only be used for specific use cases. For example, for master data, I would want to pick keys using an RDBMS, but for attachments, I would choose MongoDB. Other than that, I am more familiar with RDBMS databases.
For how long have I used the solution?
I have experience with MongoDB for three to four years and am an end-user of the solution.
What do I think about the stability of the solution?
It is a stable solution. Stability-wise, I rate the solution a nine out of ten.
What do I think about the scalability of the solution?
It is a highly scalable solution. In fact, a friend of mine who works as a stock market analyst and operates using one of the popular websites in India also uses MongoDB for his work and finds it very efficient. Scalability-wise, I would rate the solution a nine out of ten. From my end, only four to five people use the solution, but from my organization's perspective, around 500 users are utilizing it.
How are customer service and support?
We used to handle technical support ourselves, as the tool was easy to handle, and we didn't need any special assistance. Although we never had to interact with technical support, I would rate it a nine out of ten.
Which solution did I use previously and why did I switch?
Previously, I used RDBMS but found it a bit slower. That's why I switched to MongoDB for analytics purposes. I had also tried using MySQL long back before using ClickHouse, but after that, I didn't use MySQL again. While using MySQL earlier, I faced some performance issues while writing a lot of entries. So I shifted to MongoDB, which has been working well for me. Although MySQL is an open-source solution, its performance was lagging. I also tried using Oracle, but it was a costlier option.
How was the initial setup?
The initial setup of MongoDB was easy for me, and I found the community support to be very helpful. I rate the initial setup process a nine out of ten. The deployment process was also quick and only took a day or less. All that was required was to install the solution, which didn't take much time. I deployed the solution on my own, and it doesn't require any maintenance. As a friend and I only use it, it is for personal use only.
What's my experience with pricing, setup cost, and licensing?
I chose MongoDB because it is cost-effective compared to Oracle, which can be expensive. In addition, MongoDB has good performance and has not caused any issues while working with it. It has been a good choice for me.
What other advice do I have?
I recommend MongoDB because I haven't experienced any issues with it so far. Therefore, I would definitely recommend it to others. I wouldn't give the tool a ten out of ten since there is always room for improvement. I rate the overall solution a nine out of ten.
showing 11 - 16