Efficient use of NoSQL!
What do you like best about the product?
Apart from many other NoSQls on the market, MongoDB also stands out with its speed and efficient indexing method. Also being integrated with MongoDB Compass makes it easy to play around with the data.
What do you dislike about the product?
MongoDB is good for proffesional work but MongoDB Compass interface can be sometimes hard to use.
What problems is the product solving and how is that benefiting you?
As the nature of NoSQL, handling data in our projects, creating schemas are good for our usecases.
Among the best database solutions out there, and it's really useful
What do you like best about the product?
Our application development and data analysis initiatives have relied heavily on MongoDB, a highly scalable and versatile NoSQL database, for its ability to efficiently manage unstructured and semi-structured data. The database provides a feature called indexing, which assigns a unique ID to each row. I've found this to be very helpful in today's world, where web services process massive amounts of data and better storage and resource utilization is essential; in addition, its aggregation capabilities allow me to perform complicated, resource-intensive queries at lightning speed.
What do you dislike about the product?
Starting and writing aggregations in MongoDB can be challenging without a good tool to guide you. You'll also need a basic understanding of databases and SQL queries to understand the concepts.
What problems is the product solving and how is that benefiting you?
The horizontal scalability of MongoDB was a key factor in our decision to use this technology, and I must say that I have made great use of this tool. Our database scaled effortlessly, allowing us to add nodes to our cluster without sacrificing speed, which has been great for our data storage needs. As a result, we can now manage dramatically higher data volumes and workloads without sacrificing performance. It has allowed us to automate the turnaround time in our development department, which has greatly improved the feasibility of projects.
MongoDB
What do you like best about the product?
One thing is that its a NOSQL database, meaning no schema required. Also, main thing i liked in mongodb is simplicity. We can define our data through objects (like document format or the json format). Interface of mongodb is calm and greenish making it very easier to create, edit and deliver the data. Also, there is this thing called "sharding" which i learnt in my studies, what happens is the high amount of data can be shared across multiple servers. This was the coolest thing i got to learn.
What do you dislike about the product?
Well. dislikes about mongodb, is linked to the disadvantages of nosql itself. Not particularly the mongodb, as the nosql doesnot require any schema to be defined. so in my personal experience, i used to get frustated when i noticed many object data got messed up. As i switched from sql. the table format habit was printed in my mind for months, took some while to understand the hierarchy of data being created in the nosql format or rather json format in mongodb (might say complex nodes affect the data).
What problems is the product solving and how is that benefiting you?
So i was working on a project where we needed to show updates on the app as soon as they happened. It was important because our app had to stay current with new info all the time. So we picked mongodb as our database. Also when more users had to use the app, we could add more mongodb servers easily without any crashing or slowing the app down. Obviously its a database, it helped to store large amounts of data organized in this json format. If you are working on a real time project that needs to show updates quicker, mongodb is a great choice!
Future of Databases: A Critical Review of MongoDB
What do you like best about the product?
What I like best about MongoDB is its flexibility. Most of the database require fixed schema bt MongoDb allows you to store data in a more dynamic way and document based format. This document based structure is very straightforward and very easy to use even for the newcomers. It is very flexible.
Also setting up MongoDB is quick and it integrates very easily with other platforms.
MongoDB offers strong customer support, with plenty of documentation, community forums, and professional support options. Because of all these features it is frequently and widely use across the globe and industries.
What do you dislike about the product?
However MongoDb is less efficient for complex queries and transactions than traditional databases. Also while handling lare datasets it require very large memory and storage which can be costly.
Proper indexing in MongoDb is also very crucial. Also sometimes it leads to data redundancy.
What problems is the product solving and how is that benefiting you?
MongoDB solves several problems related to data management. Earlier traditional databases required a fixed schema which made difficult to handle large data. MongoDb allows flexible schema which allows us to easily change data models without much downtime.
Also there was problem with scaling and it was very costly. MongoDb solved this problem also. It can be scaled horizontally by adding more servers in les cost.
It handles large volumes of data without degrading in performance.
MongoDB - A highly scalable NoSQL Database Solution
What do you like best about the product?
MongoDB is the leading NoSQL database solution. It provides a high schema flexibility as MongoDB’s document-based structure allows for a highly flexible schema design.
One of the key features of MongoDB is it supports horizontal scaling through sharding, which allows data to be distributed across multiple servers. This is the reason for its high scalability. It is also cross-platform compatible and has a large and active community, providing a wealth of resources, tutorials, and forums.
What do you dislike about the product?
For users transitioning from relational databases, MongoDB’s lack of native SQL support can be a drawback. It may require additional learning.
What problems is the product solving and how is that benefiting you?
During my internship at Advit RealInfo, we were working on building a CMS for the organization. We ended up utilizing MongoDB since MongoDB’s flexible schema is ideal for content management systems where the structure of stored data can vary widely. It allows for easy storage and retrieval of diverse content types such as the document-based financial data we were working with, without strict schema definitions.
Offers other benefits like high performance, document-oriented storage, and flexibility in data modeling
What is our primary use case?
We use an application called Fully Factory in the Indian stock market. It works by setting price ranges for stocks. For example, if the Bank of India stock sells between 800 and 810 rupees, you set a range of 800 to 850 rupees. The system prioritizes buyers with the lowest price and highest quantity.
MongoDB's "find first" function quickly locates and blocks the remote and quantity. The client's amount is shown in the record, and then it's processed. We take around 500 records, and the first 100 are processed in a batch. This gets executed and recorded. Developers handle tasks like JP, AR, and AP separately. We update the client's inventory and pass it to a third party. In Microsoft, we use the same client cover to determine the quantity and product details. This is then executed in their API Acondra server system.
So, MongoDB Atlas is used in stock market applications to handle large-scale data processing.
What is most valuable?
For security reasons, I prefer MongoDB Atlas. It supports role-based access control, so you have an entity for each individual.
Spring Cloud ensures I have this set with Atlas, and Spring Security is entering the security for me. That's why I feel Spring Security is much better. Even if you expose a public method, it will be exposed via an authentication token.
If you're putting a direct authentication case authentication with their sync of Google token, just put a sync token directly. It will automatically type your method. Even if you expose a public method, it will be exposed via authentication token. Unmasked analytics, you have PeerSpot on or authentication token. It won't get executed.
What needs improvement?
It's better to use the predicate in Java side to sort. If you are trying to sort in MongoDB, the comparator of Sandal will be discussed. It can be sorted, but if you can do the competitor in Java, sorting using predicates (filtering conditions) and all, it'll be faster. That is what I noticed. For conditioning sorting in MongoDB might be slower, but I haven't verified that. I am doing sorting using predicate in Java.
Another concern:
When I use RoboMongo with MongoDB, it gets delayed and slower when the records are more than one billion. If the records are more than one billion, the document page will see it's all documents. If you have more than a thousand series in your system, it will be difficult to scroll down and get the reserve the directory. I think if they can have some horizontal way of displaying the reports, they can't be answered, but I'm not sure. The tool is providing protected. However, in RoboMongo, it is tough to see that, of course. It's better at one thousand or four thousand since in a single row.
For how long have I used the solution?
I have experience with this product. I've used MongoDB intermittently since around 2020. It's a deep system. You need to find the data, and sometimes use queries. There's a conversion tool that helps transform static queries into MongoDB 3 format.
What do I think about the stability of the solution?
In RDBMS, we have an option to put triggers and functions in the database. In MySQL, you have an option to put a function as well as a trigger, but I haven't found that option in MongoDB. I can create functions, but I am not able to create a function trigger there. We have to create, get, update, and delete, which I can do in MySQL and SQL Server also. But in the same way, you can perform in MongoDB. That is the only thing I noticed.
Other than that, the query that is performing, creating, updating, and deleting everything can be made possible in MongoDB. You cannot create only that trigger in MongoDB. I haven't found anywhere to create that trigger.
Without triggers, you can't automatically execute actions in response to data changes in MongoDB.
That is the only drawback that I find with MongoDB: creating the trigger. Apart from that, I think everything can be possible. We can put function software into the database, and you can execute the review. But when creating the triggers, you need to perform separate functions for that.
What do I think about the scalability of the solution?
Scalability in MongoDB always depends upon the configuration. We can configure it accordingly, but it is definitely essential.
Your hardware system should also ensure the number of resources your application is consuming. For example, in my application, if the unit is more than 400 kits. In a point of time, it will get executed.
I tested that using JMeter. When I'm doing the amenity services, I always put the 500 resource at a time. At a single point of time, 500 resources will get in that 5, so I just find any issues on that. The client also has not had any issues.
When we are doing any of the microservices, we need to ensure using JMeter. Via JMeter, you can ensure, like, how much on the port of ten, how much in the source can be accessible.
How was the initial setup?
It's a one-click install. Maybe, like, two settings. If you already have MongoDB, five to ten minutes is regarding some MongoDB. The only thing that you should know is the port number and the IP address if you're exposing your application to a third party. I think if you're aware of those risks, you can install it immediately. It's easy if you need to collect that data. You might know five to ten minutes.
We can install the remote engineer system. I don't think it will be a bigger task, but even if you're configuring for multiple people, you just need to add that particular port number in your system. Otherwise, it won't allow you to log in.
Even if you're using Microsoft authentication, we normally have multiple layers of authentication. So use the command password, and then you will get the notifications, whether you are getting log-in or not. That will take some time.
Maintenance:
For getting queries only, we put a Java set. From the development perspective, once the database is set up and you configure the URLs, everything works fine. You have 192.138.1.1 URL, it automatically connects to the review if the network is enabled. Then it connects to the review. However, it definitely depends on the bus service we are passing. It should work fine with no issues if the configuration is okay.
That is how we install it. Once we have source, then it's the same network. If it is on the same network, we have a contract, the traffic is there, and the agent works.
If I want to test whether my microservices work fine, I use them again, and they test if my microservices are working fine. Normally, almost all microservices are in a rack server, so you don't get the performance there. I haven't found any issues directly.
What other advice do I have?
If you are looking for a robust system with a lot of security concerns, then you should go for IBM. I'm not saying MongoDB is not 100% secure, but for highly confidential data, I would suggest other solutions.
However, in MongoDB, you can do filing processes and vertical reports. Everything can be done in MongoDB, but the newest is a relationship. You cannot maintain the referential integrity relationship. You can maintain it, but it will be a little tough.
If you want to maintain the relational database in MongoDB, the resource should be at least a minimum of one and a half years highly exposed in MongoDB. Then only we'll be able to manage that data. Even for new joiners, it is a little tough to explain how the relational database is maintained in MongoDB.
Overall, I would rate the solution an eight out of ten.
Reviewing MongoDb
What do you like best about the product?
MongoDb Atlas free hosting platform to start with project is the best. It's simplicity to connect with project makes it easy to use with different backend languages.
What do you dislike about the product?
Didn't found as such, overall it's good.
What problems is the product solving and how is that benefiting you?
I personally use mongoDb in most of my full stack application. Using MongoDb, atleast my hosted application I could show off during interviews.
MongoDB best NoSql dabase management system
What do you like best about the product?
What i like most about MongoDB is that it is very easy to use, when i worked with React and required to retrieve or store data i integrated MongoDB with Nodejs.It has document based schema which makes it look much easier.
What do you dislike about the product?
It does not support ACID properties. And it slows down when inconsistent or unbalanced data is shared.
What problems is the product solving and how is that benefiting you?
To handle data for applications which requires to store and retrieve data easily and faster, MongoDB is the best Database management system for such applications .
