Non-relational Database

Running head: NON-RELATIONAL DATABASE
Non-relational Database
Name of the Student
Name of the University

NON-RELATIONAL DATABASE
1
Use of the embedded reference approach in order create association
For this project the embedded reference model is used in order to create the
relationships. For better data base operation performance in terms of storing as well as
retrieval of data in a faster way, it is tried to always embed different child documents in an
document except when it is necessary or important for the sake of the applications. With
the embedded approach, it eliminates the requirement of performing separate queries in
order to retrieve embedded child documents. While inserting the child documents the array
of elements concept is utilized at the time of embedding in the parent documents. This use of
array is helpful in modeling different relationships among the documents stored in the
collection.
Embed documents are also maintained together. Whenever, any of the
records/documents are queried, or updated all the elements are done together inside the
embedded document. Dependency among the documents are the key indicators in order to
embed a document inside a collection. For example, in this project the developer details are
solely dependent to concerned game itself; thus this data and developer data should be kept
together.
Advantages and disadvantages
The Reference between the documents are done for only those documents that are
highly volatile in nature. The high volatility the more the documents requires reference and
relationships among them to be modeled using the embedding technique.
Along these lines the data retrieval winds up productive and is by all accounts a
decent approach at the principal look. In functional situation in some cases this methodology
can be suitable one, however relying on the embedded relationship models can make genuine