We use it in our virtual environment.
Our software produces a lot of predefined JSON Structures. We save those JSONs in an encrypted form inside MongoDB.
It's simple storage of JSON. We do not perform any database functions.
We use it in our virtual environment.
Our software produces a lot of predefined JSON Structures. We save those JSONs in an encrypted form inside MongoDB.
It's simple storage of JSON. We do not perform any database functions.
In our case, it is most important to have redundancy. It supports a replica set and it allows us to use mutual TLS for authentications with the certificates.
The documentation is useful.
We work with the community edition and it would be really nice to have for the database side encryption, but it's not available in the community. It is only available in the enterprise edition.
We use mutual TLS, which means we use the certificate for authentication and connection encryption.
When I want to connect to a node, I need to supply the certificate that MongoDB trusts, even though I use an admin password. This is not useful, and it complicates things.
It would be much more useful if I have an admin user and a password.
I would like it to be more straightforward when connecting to a node.
We have been using MongoDB for the last 12 months.
We are using version 4.4.0.
It's pretty stable. We don't have any complaints.
It's a scalable solution. We haven't had any issues.
We are in development mode, and not really used by users. We have five people for development.
We can't know for sure if we will continue to use this solution. We are still in the development phase so we have to see when we finish.
I have not contacted technical support. I used the official documentation, which was enough for me.
The initial setup was straightforward. We used Docker, so it was pretty easy.
It didn't take long to deploy.
It's free. It's a community edition, so we do not pay anything.
There are no additional costs.
We didn't really evaluate other solutions. We did not have strict requirements in choosing a database. We just needed to keep JSON files informed when we produce them and MongoDB seems to be fine for us.
I would rate MongoDB a nine out of ten.
We use MongoDB for monthly billing of the mobile software we provide to our client, Talent Post. It includes the services they use on their mobile devices.
One of the biggest benefits is the speed and flexibility of the documents, especially when it comes to modifications. It has definitely helped us to function more efficiently.
The best advantage of MongoDB is the flexibility and scalability of the database.
There is a need for improvement in MongoDB's customer support, better support would be great.
Another feature that I haven't discovered yet but would be useful is a backup and restore process that can handle large database sizes. Right now, I have over three terabytes of data, including logs, which takes a lot of time for snapshot backups.
I started using MongoDB a couple of months ago.
The overall performance is faster than a relational database like SQL. But, the equation function in MongoDB is not as clever as the stored procedure in SQL. It's more complex to write the functionality like a stored procedure in MongoDB.
I would rate the performance of MongoDB a five out of ten.
I would rate the scalability an eight out of ten. I have around 2500 branches of users that use MongoDB simultaneously. We plan on increasing the usage.
I would rate the initial setup a six, where one is for easy and ten is for complex. It is a little complex. It's more complex when we think about deploying MongoDB with the shopping feature. But setting up MongoDB without consideration of shopping would be easy.
The deployment would take a day, but that includes testing. We didn't use any third parties. We deployed the solution ourselves.
I would rate pricing a seven out of ten. It is a bit costly.
I would definitely recommend using the solution.
Overall, I would give it a seven out of ten. The reason is the flexibility it offers, especially for deploying solutions for mobile services. Additionally, it's still considered a new technology in our country, so it's quite trendy.
We are using MongoDB for unstructured databases.
The most valuable features of MongoDB are we have a lot of documentation and SQL-based applications that run on it.
MongoDB could improve by not having so many updates and different versions.
I have been using MongoDB for approximately two years.
MongoDB is stable, but there are always a lot of patches and upgrades every now and then.
MongoDB can scale but you will need to pay for the upgraded solution.
I have not contacted the technical support of MongoDB.
The initial setup of MongoDB is simple and the implementation took approximately one day.
We did the implementation in-house.
MongoDB is a free solution. We wanted to have high availability and the subscription cost was quite expensive because the basic one is free and then when you want to have some other replications or other features you will need to pay money. Overall the solution is expensive.
I would recommend this solution to others.
I rate MongoDB a six out of ten.
We recently had customers asking about MongoDB, so we have started to deploy new environments for that. We have implemented it may be four times. We are implementing it for our customers in our own infrastructure. We have done on-premises as well as cloud deployments.
Our database team works on the use cases. I work only on the implementation part. I am responsible for getting the clusters up and running. I'm just managing the server and guaranteeing that the clusters are up and running and backing up. I also handle the monitoring.
It is very easy to create a MongoDB cluster. You can deploy three nodes in one hour.
You can do small configurations to enable routing. It is easy to implement.
It should have GUI for managing clusters. MongoDB needs a more powerful GUI to manage clusters and make switchovers. Currently, there is no good, free tool to check the replication to find out if there is a gap.
It is very stable.
It is very scalable. You can add nodes every day to the replica.
I have no experience with technical support.
It is easy to implement. One person can manage ten managed MongoDB clusters.
At the moment, all customers are using the community version.
I would highly recommend this solution. I would rate MongoDB a nine out of ten.
We use it for website designing, and for mobile app designing just like Adobe XD. This is back-end technology that helps in integrating the front end with the back-end systems.
I value the API integrations.
I would like to see the scalability and security improved.
I have been using MongoDB for the past two years.
MongoDB is a stable solution.
It is complex and you need some expertise to deploy it.
We did our deployment in-house.
MongoDB has an open-source model.
I would rate MongoDB a nine out of ten.
We primarily use the solution for long-term storage. We use it to store all our data. We also use it to support microservices that already have calculated data. We don't use it for any other purpose.
The most valuable feature of the solution is the ability to easily store documentation regarding structures.
We can easily connect to MongoDB and search without transformation, without joining. If we want to use a simple search it's really fast.
The initial setup isn't really that complex.
The solution is pretty stable overall.
If we want to perform some joins or some other types of transformation that are more advanced, in that case, we cannot use MongoDB. We need to use another solution.
The solution needs to better support modern aspects of search engines. There is typically a microservice layer and MongoDB doesn't support well within search engines. If you want to create some complex structures, you need something like Elasticsearch, for example.
The pricing is expensive.
MongoDB should better support small and medium companies. There are a lot of clients out there that are interested, however, they need something lighter and less complex and something not so expensive upfront.
I've been using the solution for the past two or three years.
The stability of the solution is very good. There are no bugs or glitches. It doesn't crash or freeze. It's pretty good overall.
I've never used technical support. I can't speak to their level of responsiveness or how knowledgeable they are.
We previously mostly used SQL databases. We used Microsoft SQL mostly and we needed some NoSQL databases. That's why we implemented Elasticsearch and MongoDB. We wanted a NoSQL database that we could search, however, was also capable of long-term storage.
The initial setup is not so complex when we are talking about on-prem solutions. It's an easy initial setup. We are fine with that.
I was surprised, however, by the lack of support offered during implementation. You are left to your own devices. There isn't much guidance - especially on so complex a transformation.
We have our own agent teams. Mostly we rely on our engineers, not consultants at other companies. We're able to handle everything rather well in-house.
The pricing is quite high and we don't appreciate the solution raising prices so much.
I'm following up with the licensing, however, I don't have the exact figures right now. I mostly advise some companies about that, and usually do not go into detail. What I'm interested in, for example, is when you implement some solution in some company what are the costs for that company in the near future, for example, in one or two years. This is what we are thinking about.
It's not easy to implement some solutions in some small companies if at the beginning they need to pay some licensing costs upfront. For example, for Mongo DB. It would be easier if the small companies could operate without licensing for some period of time and then only after they grow to a certain size or need they would have to pay some for that usage.
While I may advise clients on MongoDB, I don't have a direct business relationship with the company.
We always use the latest version that is available.
As we implement the solution for clients, we deal with different deployment models. Typically, for banks, for example, the on-premises deployment is used. However, we've looked into the cloud as well and some clients may consider that deployment instead.
A company considering the solution needs to first think about the project and the infrastructure that they need to implement. Every solution is different. I cannot say that I feel some particular way about MongoDB. It always depends on the organizational need.
I'd rate the solution at a seven out of ten. I'd rate it higher if it offered more upfront support and a lighter solution for smaller organizations. It would be great if they could build an open-source version, for example.
Our primary use case of this solution is to directly monitor public services.
I like that this solution helps us to manage our allowed time on the release date or entry, but if you have a conventional application where you have to make a lot of queries with the joints, you have to mix the information of several tables. You cannot go to a non-relational database, you have to go to an Oracle or MariaDB or whatever. But if you have other queries like smaller tables with a lot of resistance, MongoDB will be okay.
MongoDB is very valuable for us due to the large amount of entries that we can install in the database. The solution makes it very easy for us to develop with these databases. It is also easy for development and to list all our entries in a single table.
We find it difficult to incorporate MongoDB in some projects. It's also very complicated to join different tables. For example, MongoDB works very well with the note GS Java Script. But when you try to develop in Java, it is not so easy. So the integration is not very simple.
My colleagues, however, reported that it's easy to manage the database. I also know that it is very easy to make an application in Java scripts.
We haven't had any issues with stability since we started using this solution two years ago.
We're not currently using the alert implementation of MongoDB, but it's enough for us and we can escalate to put in more machines if we like. We are not using that many implementations.
We don't use the technical support because we have our own technical team that can help us.
We use MariaDB as the main product of the company, but we find it difficult to fine-tune the database and to increase our services. We also have problems with queries. So we implemented MongoDB with MariaDB because MariaDB doesn't have the same capabilities and now we can do some fine-tuning of the database.
The initial setup was very easy and we did everything ourselves.
My advice to others would be not to use MongoDB for complex business applications or difficult queries. There are some integration issues that need to improve, so I will rate this solution an eight out of ten. Still, it is a very good product that is user-friendly and it works fast.
We just recently downloading the product and we were trying to do the migration and it worked well. We use it as an individual level only, small projects, and small migrations. We have completed a full project yet.
One of the most valuable features is the ability to Text Search can be used anywhere and anytime.
I have found the solution difficult to operate as an administrator. They could improve the experience by adding some more features to the UI. There needs to be better integration, we have been having some issues with some projects.
I have been using the solution for the past year.
The solution has been scalable so far for our level of raw data and we expect it will be good even if we complete the whole project.
We have used SQL Server and Elasticsearch in the past. SQL Server was easier to manage as an administrator than this solution.
The installation of the solution was not an issue for the client or the server.
The solution is straightforward to download and install. However, configuring is what takes time. For a small migration, there were approximately seven people involved. We all spent some time learning the new product.
If you want support with the solution you will need to purchase a license and not use the open-source version. The license is a little expensive.
Going by my level of experience in these solutions I would recommend it to others.
I rate MongoDB an eight out of ten.