Data Scientist at a financial services firm with 10,001+ employees
Real User
Top 20
2024-03-22T15:59:55Z
Mar 22, 2024
If someone is working on a project that requires JSON, they might prefer using MongoDB. The choice depends on the project and the data we use. The product is good overall. There is an issue with installation, but the processing is fast, and we can update large amounts of data. If we need more analytics, we can choose MongoDB. Overall, I rate the product a seven out of ten.
Leiter IT / Business Support at a comms service provider with 51-200 employees
Real User
Top 20
2023-10-20T08:34:09Z
Oct 20, 2023
It is a good foundation for the data. It’s a good solution. We'd not recognize it until it fails, and it does not fail so often. Overall, I rate the product a nine out of ten.
OSS Automation and Orchestration Consultant at a comms service provider with 1,001-5,000 employees
Real User
2020-08-27T10:31:48Z
Aug 27, 2020
The only advice I can give to anyone looking at NoSQL is just to focusing on the dimensioning before starting any project. I have had some experiences in over-dimensioning and under-dimensioning in some projects. Investing in the dimensioning with respect to performance is the key to success. On a scale of one to ten where one is the worst and ten is the best, I think Oracle NoSQL would be an eight. This is mostly because I think this Oracle is not a cheap product. I think that the licensing is expensive and this is means sometimes people will just try to avoid using Oracle based on cost alone. In other words, it is usually the financial rather than the mechanical restrictions that make a customer choose a different solution.
NoSQL databases represent a major departure from traditional relational databases. They are designed to handle a wide variety of data models beyond just relational data, including columnar, document, key-value and graph formats.
If someone is working on a project that requires JSON, they might prefer using MongoDB. The choice depends on the project and the data we use. The product is good overall. There is an issue with installation, but the processing is fast, and we can update large amounts of data. If we need more analytics, we can choose MongoDB. Overall, I rate the product a seven out of ten.
It is a good foundation for the data. It’s a good solution. We'd not recognize it until it fails, and it does not fail so often. Overall, I rate the product a nine out of ten.
I rate Oracle NoSQL nine out of 10.
The only advice I can give to anyone looking at NoSQL is just to focusing on the dimensioning before starting any project. I have had some experiences in over-dimensioning and under-dimensioning in some projects. Investing in the dimensioning with respect to performance is the key to success. On a scale of one to ten where one is the worst and ten is the best, I think Oracle NoSQL would be an eight. This is mostly because I think this Oracle is not a cheap product. I think that the licensing is expensive and this is means sometimes people will just try to avoid using Oracle based on cost alone. In other words, it is usually the financial rather than the mechanical restrictions that make a customer choose a different solution.