The fact that relational databases are not good at doing so is the reason why NoSQL is Born:
- Large number of data write operations
The book is written "large amounts of data write operations", I understand that should be "a large number of data write operations", because a large number of data write operations will cause concurrency, concurrency and locks are relational database bottlenecks, NoSQL split the table to different nodes, you can distribute the write operations to each node.
Why can't a relational database solve a large amount of data write operations? In the aspect of data reading, the relational database can increase the pressure of high concurrency by increasing node and master-slave replication. However, in terms of writing, to ensure consistency of data on each node, the write request is still sent to each node, and the pressure cannot be decomposed to each node. At this point, if you consider splitting the data table on each node, you cannot guarantee the join operation of multiple tables.
- An app that doesn't have a fixed field
Better understand not to repeat.
NoSQL database Technology Combat-the 1th introduction to NoSQL and Big data why NoSQL
