External reviews
External reviews are not included in the AWS star rating for the product.
Audio embedding resources
I’d like to suggest adding more resources on using audio embeddings with MongoDB's vector search. Additional guidance on best practices and examples would greatly benefit those looking to work with audio data in MongoDB.
- Leave a Comment |
- Mark review as helpful
Powerful and Flexible Database for Gen AI Projects, with Room for Onboarding Improvements
Creating Mentation, an AI-driven wellness assistant, was an enriching experience, and MongoDB supplied the foundation we required for effortlessly handling intricate and diverse data. By managing user interactions and emotional data as well as processing vector embeddings, MongoDB effortlessly fulfilled our requirements. Its adaptability and scalability proved essential, allowing us to broaden our project’s scope without having to repeatedly reconfigure the database.
Although the documentation is comprehensive and addresses various use cases, a concentrated, beginner-friendly crash course would have been immensely helpful—particularly for teams such as ours seeking to utilize AWS and Gen AI. Exploring the fundamentals of MongoDB, such as querying, vector indexing, and aggregation pipelines, prompted us to seek out external tutorials, especially to clarify information regarding vector indexing. At one stage, we came across contradictory data from these sources indicating that solely larger M10 clusters were capable of handling vector indexing, which resulted in additional testing and problem-solving.
Although there were some learning challenges, MongoDB demonstrated to be a robust solution for the requirements of our project. By providing a more efficient onboarding process—centered on key elements and better instructions for utilizing features such as vector indexing—MongoDB would become even more attainable for developers engaged with advanced technology. In general, we had a positive experience with MongoDB, and with some modifications, it could easily become the preferred choice for any developer venturing into Gen AI applications.
Improvement on Documentation
For my hackathon project, I chose MongoDB Atlas from AWS Marketplace. I particularly like the auto-scaling capability.
However, I encountered some challenges with the SDKs at multiple stages of use, so I had to look outside the official documentation for help. For example, while connecting to the cluster.
While the existing documentation is okay, it would be more beneficial if video resources were included (as this helps better than textual documentation). Additionally, integrating real-world examples and case studies into the documentation could greatly enhance its practical value.
The best solution out there
I've used mongodb professionally for 4 years and have found the product meets and exceeds the demands placed on it by the products i create.
You can start quickly on projects which allow you to store many things
Any business types where we need instructional data.
How has it helped my organization?
In a previous company where I worked, we were able to use MongoDB as a pure data storage using the block storage mechanism for our clients.
What is most valuable?
You can start quickly on projects which allow you to store many things.
What needs improvement?
I would like a more comprehensive dashboard. The UI can be difficult to understand.
Going forward, we would like to have pure AWS Cloud (native) storage instead regular storage on the AWS integration side.
For how long have I used the solution?
One to three years.
What do I think about the stability of the solution?
The stability is very good.
In my previous company, we had a lot of data coming in every day, and the product remained stable.
What do I think about the scalability of the solution?
We have been able to scale from gigabytes to terabytes easily.
How is customer service and technical support?
I have never used technical support.
How was the initial setup?
The integration and configuration of MongoDB in the AWS environment is quite good.
What was our ROI?
In my previous company, the product allowed use to build a database in a highly regulated environment with the ability to get distributed storage. We used MongoDB as a distributed storage to set up this environment for a critical business application with millions of dollars.
Which other solutions did I evaluate?
My advice is make developers understand NoSQL databases. For people coming from the SQL world, this is a new way to develop applications and that is the point to focus on. In the NoSQL world, MongoDB is a product that has a good awareness and has proven to be very good.
Our clients also evaluate Cassandra or other key value storage vendors. Its depends on what they want to do exactly. MongoDB is somewhere in the middle between pure key value and something like Cassandra, which is designed for bigger deployments.
MongoDB is fortunately well known now in the development community and has a good framework for languages, which is why our clients chose the product.
What other advice do I have?
We are always integrating this product with our business applications because it is a database. Without our applications, the product doesn't make sense. The integration is quite straightforward, because of the consistences within MongoDB, you can find where to connect it.
It is nice because our developers create tables whenever they need to sync data
We use it for all of our temporary data, anything which is not warehoused.
It works with AWS Lamda and EC2.
How has it helped my organization?
It is nice because our developers create tables whenever they need to sync data. There are allocations nor DBAs. It is just use it as you need it.
What is most valuable?
* Autoscaling
* No overhead
* No maintenance
What needs improvement?
We had some bad trainers when we first came onboard and would rate them fairly low. They did not seem staffed properly to fulfill the training services that they offered.
For how long have I used the solution?
One to three years.
What do I think about the stability of the solution?
It is very stable. It has been running without issues.
What do I think about the scalability of the solution?
We have about 2000 customers a day.
What's my experience with pricing, setup cost, and licensing?
The pricing is good. We originally chose it over DynamoDB because of the pricing.
Which other solutions did I evaluate?
We also looked at DynamoDB from Amazon. However, it didn't have the features that we wanted from MongoDB.
We chose MongoDB based on its pricing and features.
What other advice do I have?
I have been happy with the service. Everything is good. Though, nothing stands out to me as exceptional.
I would encourage someone to look at DynamoDB, even though I am fine with MongoDB. If you are in a fully integrated into the AWS environment, you might want to stick with Amazon Web Services rather than a third-party.
The integration went well and was lightweight
It is one of the main database back-ends for one of our products in the company.
How has it helped my organization?
* It has a flexible integration with our easy API.
* It has a good, easy integration with other tools that we use for this product.
What is most valuable?
* Flexibility
* An easy API
* Its redundance: We have a cluster of three very solid instances, so its very reliable.
* The integration went well and was lightweight.
What needs improvement?
During the configuration, we did some migrations where we had to reindex about 70,000 indexes, which took around an hour. They should improve this and optimize the indexing.
For how long have I used the solution?
One to three years.
What do I think about the stability of the solution?
We have good impressions of the stability.
We are good as far as the stress that we place on it. This is one part of the product that we are not worried about.
What do I think about the scalability of the solution?
The scalability is good. We use a three instance cluster for this installation, and it works great. Therefore, we haven't had to touch it for awhile, which is good.
How was the initial setup?
Our backups required some configuration.
Which other solutions did I evaluate?
I did not evaluate the product because I am on the operations side and the design was already done.
What other advice do I have?
Look at what MongoDB can do for you in terms of database back-end persistence. I would recommend to look at this first before you start looking at other solutions.
My company is interested in putting out products that are reliable for our customers, which we can monitor easily. We also want them to be easy to install and deploy, which is why I am happy with this one.
We are running this on an AWS instance.
Its most valuable features are high availability and zero maintenance
* High availability
* Resource recovery
How has it helped my organization?
It brought a lot of confidence to our team.
What is most valuable?
* High availability
* Zero maintenance, to double up things.
What needs improvement?
The cost needs improvement. The product is good, but the cost that we paid for it is expensive, so it wasn't that valuable.
For how long have I used the solution?
Less than one year.
What do I think about the stability of the solution?
The reliability is good.
What do I think about the scalability of the solution?
It is reliable. We have a small environment right now.
How was the initial setup?
The integration and configuration of this product in our AWS environment were easy and straightforward.
AWS works well with this application, but that is the only thing we have tested. We are happy with it.
What's my experience with pricing, setup cost, and licensing?
Purchasing through the AWS Marketplace was easy and seamless. We chose the AWS Marketplace because it is a brand name and a popular product.
It is too expensive. They need to work on this.
Which other solutions did I evaluate?
I also evaluated the open source version of this same product, but chose the AWS version for more reliability and enterprise support.
What other advice do I have?
I would recommend the product.
It was easy and quick to market in terms of getting the application deployed rapidly
It drives a good portion of our client-facing software utilities.
What is most valuable?
* Scalability is its most valuable feature, as it is pretty simple.
* The maintenance is fairly easy.
* It was easy and quick to market in terms of getting the application deployed rapidly.
What needs improvement?
The cost needs improvement.
For how long have I used the solution?
Three to five years.
What do I think about the stability of the solution?
The stability is fine.
How is customer service and technical support?
We use technical support quite frequently. The tech support experiences that I have heard anecdotally have been fine. I haven't heard about any issues of getting problems resolved.
We are mostly using technical support because of changes in deployments and learning how to configure new things. While a lot of the work is done in-house, it is more about extending the capabilities of our internal team.
What's my experience with pricing, setup cost, and licensing?
Pricing could always be better.
Which other solutions did I evaluate?
I am sure that they evaluated other products, but it's been in deployment since I have been with the company. Therefore, I don't know if they looked at other types of databases at that time.
What other advice do I have?
It is a great product. It works fine, so we recommend it. We are continuing to use and expand it.
Right now, MongoDB is deployed for a very specific use case. However, it is something that we always consider when we are looking to migrate away from traditional RDBMS, like Oracle and SQL Server, then MongoDB is on the top of that list. We see if it is capable of supporting the app as written.
I was not involved in the implementation or configuration.
Our queries are quicker with it. It is also very easy to use.
We use it for hosting data on the cloud.
How has it helped my organization?
It enables us to get work done quickly and get to our data. It benefits us by providing performance.
What is most valuable?
* As a user, it is very easy to use. There is nothing complicated.
* We can write queries and go through it very quickly; our queries are quicker with it.
* Many tools are there. Other companies are providing many tools for getting to your MongoDB.
What needs improvement?
The import and export process needs improvement, i.e., getting in and out. Moving data from other databases into MongoDB, along with indexing, was challenging. However, it has been improving.
I would like them to make the product easier to use.
For how long have I used the solution?
Three to five years.
What do I think about the stability of the solution?
We are happy right now with stability unless something goes wrong down the line. In that case, you have to bite the bullet.
In terms of workloads, we put 60 to 80 percent on it.
What do I think about the scalability of the solution?
So far, so good. However, we have had issues with our VPC, and how we have stored on S3 and our instances that we have with MongoDB. We are learning as we are building more capacity.
Our environment is utility customers, which is millions of meters, and each one has their own instance. We obtain that data for every 15 minutes in a big city environment, which is why performance is very important.
How is customer service and technical support?
The technical support is good. We have received very good feedback.
How was the initial setup?
The integration and configuration were pretty easy. We loved it. Otherwise, we would have changed databases.
What was our ROI?
We have definitely seen ROI.
What's my experience with pricing, setup cost, and licensing?
The purchasing process through the AWS Marketplace was very good.
Which other solutions did I evaluate?
I was involved later on in the evaluation process when we were looking to import and export data out of MongoDB. We looked at MySQL, but we wanted to be on the cloud instead of managing our data on MySQL.
What other advice do I have?
I would recommend it. It is better than the legacy databases, and it is very good with the cloud.
showing 1 - 10