Note that the finest way knowledge is modeled in NoSQL databases can get rid of the need for multi-record transactions in lots of use cases. Consider the earlier example the place we stored information about a consumer and their hobbies in each a relational database and a document database. In order to make sure details about a user and their hobbies was updated collectively in a relational database, we might want to use a transaction to replace data in two tables. In order to do the identical in a document database, we could replace a single doc — no multi-record transaction required. In truth, compared with relational databases, many find modeling relationship information in NoSQL databases to be simpler than in relational databases, as a outcome of related knowledge doesn’t need to be break up between tables. NoSQL knowledge models allow related information to be nested within a single knowledge construction.
