My company also uses Oracle DB and MS SQL. 

We previously used another database but it was not proper for our tasks. The solution provides us with the proper resolution and results. 

We also use Oracle. Previously, a long time ago, I also used Teradata.

In Asian companies, Oracle is very expensive to use and adopt.

We started using Mongo as it was stable and easy to adopt.

Previously we used MariaDB and we continue to use MariaDB for other purposes. We started using MongoDB to manage non-relational data.

We were using PostgreSQL for everything, but it is not the best fit for our needs due to the diverse nature of our data. We switched to MongoDB, as NoSQL is better suited for this scenario.

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.

We previously used the RDBMS solution, MySQL.

MongoDB has five to ten times better performance than MySQL. MongoDB has a lot of advantages. With MongoDB, you can store any kind of data, including structured, unstructured, and semi-structured data. MongoDB has a lot of benefits over RDBMS.

I previously used MySQL and PostgreSQL, but I had permission and licensing issues with MySQL. I prefer MongoDB over others.

I have experience with MySQL and PostgreSQL, but I'm entirely focused on deep learning, so my team only uses MongoDB and Databricks. I'm not into complicated products, and I know what I can do with MongoDB and how to do it.

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.

We switched from Oracle to MongoDB because of costs. Oracle also has a MongoDB solution inside it. In Oracle, you can install document databases, which helps, and it also supports JSON and just about everything. It's one-to-one. Whatever you do in MongoDB, you can do it in Oracle. But Oracle isn't free.

The main problem with Oracle today is the price. Many companies around the world are trying to move out of Oracle because of the cost. They are not moving because the database is not good. PostgreSQL is really like Oracle, and MongoDB is like Redis, and all these have free community databases. If you want to buy the enterprise edition, it costs a bit but not as much as Oracle.

Previously, I used AWS DocumentDB and DynamoDB.

We mostly used Microsoft databases in the past. We started with Access and Microsoft SQL Server. I've also used Innovation together with SQL Server.

We did not use a different NoSQL solution prior to MongoDB.

We continue to use Microsoft SQL Server for other types of database implementations that require SQL, which I also have expertise in.

We also use Oracle and we have found that if you want to have a DR site, you need to replicate the data from one site to the other. With MongoDB, we set up a cluster on the wide-area network, and we don't have to do any data replication. Instead, it will help you with these things.

With Oracle, the user interface makes it easy to explore the database. With MongoDB, the interface is quite primitive and it is more difficult to look at the data. It is not as user-friendly.

There are a lot of vendor and third-party tools that work on top of Oracle, but this is not so much the case with MongoDB.

When I've used other DBs I found them to be inferior.

We have used also Atlas (MongoDB solution for Cloud), and MongoDB has developed a useful framework with lots of new features that are not included in MongoDB's on-premise version. If you choose a cloud DB, it's great if you are looking for a lot of innovative features. 

Many clients use SQL DBs and many are moving over to MongoDB.

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. 

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. 

We have used SQL Server and Elasticsearch in the past. SQL Server was easier to manage as an administrator than this solution.

We may have used InfluxDB for some reason but I don't recall any of the details.

I was working with MySQL before. I decided to use MongoDB rather than other products to learn something new. It is easier to learn and implement than other databases.

We did not use another NoSQL database solution prior to MongoDB.

We have used Snowflake before and I can tell you what the difference is between MongoDB and Snowflake. Snowflake is a totally different type of database. It is basically shot across small units and its solutions are only for the cloud. Your access can be private and it can be fast on the queries. Whereas with MongoDB, it takes much longer than with Snowflake if you want to extract. Snowflake is much faster. It has good analytics capabilities, though.

We have about five products that factor into the needs of the BFSI segment in India. These proprietary products developed on five or ten platforms. We don't develop MongoDB, we just use it as a storage platform.

Currently, we also use RDBMS. We use Oracle for some other products. We don't just use MongoDB exclusively.

While Oracle is better for transactional services, MongoDB is extremely good at support services. That's the main difference. I have seen people use MongoDB for transactional as well, however, I have never attempted it, so I can't speak to it's capabilities.

We also use SQL databases. We use the SQL server. We've been using it over the last year. 

I have used other databases but they were SQL solutions. MongoDB is different because it is a NoSQL solution and the structuring of data is less formal. It has to be formatted internally.

Previously, I was not using another solution. It was already in place when I joined the company.

We were also using MariaDB, but MongoDB is good for certain situations in which MariaDB is not suited for. For example, managing the database of log files is easier with MongoDB.

I recommend the solution for my current company. They have used MongoDB for two projects now. We chose MongoDB because of its community.

MongoDB is more secure than similar databases. You can pass documents from there. You can add large data in the same record. It works with PostgreSQL and the like, and it is a structural database.

We switched due to a common OS integration strategy.