I am responsible for the past, until now not used MangoDB business scenarios, but for the interest and popularity of NoSQL, reading some documents made simple to understand. In-depth study and then during follow-up be required to use.
This article does not describe specific syntax.
Basic Information
- Similar Json of BSON storage to support unstructured data
- Does not support join
- Data is loaded into memory when running
- Supports sharding
- Version 4.0 only introduced Affairs
Correspondence between the structure MySql
| The concept name | MySql | MangoDB |
|---|---|---|
| Storehouse | Storehouse | Storehouse |
| table | table | Table (set of collection) |
| recording | Row | File |
Associated standby switching
- A main more prepared
- When the primary node hang, elect a master node
- There is a special election not only read and write arbiter node
- The election may fail, at this time can only be read but not write
Lock mechanism
Prior to version 2.2, the entire library a lock
after the 2.2 version, the table lock
3.4 version, recorded level
Common scenarios
- Map data (such as high-Germany)
- Takeaway industry (distribution map related)
- Unstructured product library (Table commodities necessary to save the image, but also to keep electronic products)
- Traffic log analysis