MONGDB Usage Scenarios

You expect a higher write load

By default, MongoDB is more concerned with high insertion speeds than transaction security. If you need to load a lot of low-value business data, MongoDB will be a good fit for your use case. However, you must avoid using MongoDB in scenarios where high transaction security is required, such as a $10 million transaction.

Unreliable environments guarantee high availability

Setting up a replica set (master-Slave server settings) is not only convenient and fast, but also enables fast, secure, and automated failover of nodes (or data centers) using MongoDB.

There's going to be a big scale in the future.

Database extensions are challenging, and when the single table size reaches 5-10GB, there is no doubt that MySQL table performance will degrade. If you need to Shard and split your database, MongoDB will easily achieve this.

Using location-based data queries

MongoDB supports two-dimensional spatial indexing so that data can be obtained quickly and precisely from a specified location.

The explosion of unstructured data grows

Adding columns to an RDBMS in some cases may lock down the entire database, or increase the load to cause performance degradation, which usually occurs when the table is larger than 1GB (and the pain points in the Billrun system are mentioned below-a few gigabytes in a single table). Given MongoDB's weak data structure pattern, adding 1 new fields will not have any effect on the old table, the whole process will be very fast, so you don't need a dedicated 1 dba to modify the database schema when the application changes.

Lack of professional database administrator

If you don't have a professional DBA and you don't need to structure your data and make a join query, MongoDB will be your first choice. MongoDB is well suited for class persistence, and classes can be serialized into JSON and stored in MongoDB. It is important to note that if you are looking for a larger scale, you must understand some of the best practices to avoid getting into the wrong way.

MONGDB Usage Scenarios