Non-Relational Database Report: MongoDB Implementation and Analysis

This report analyzes a NoSQL database assignment using MongoDB, focusing on the implementation of embedded references for data modeling and retrieval. The assignment explores the advantages and disadvantages of embedded document approaches, emphasizing performance considerations and the efficiency of data access. The report discusses the use of embedded references to create associations within the database, contrasting it with other approaches. It examines the benefits of embedded documents for certain data relationships while also acknowledging potential performance issues. The report includes recommendations for database design, highlighting the flexibility of NoSQL databases and the importance of combining embedding and referencing techniques for complex data relationships. The assignment also covers the design of the database using MongoDB, the creation of relationships, and the merging of different techniques to ensure efficient data retrieval.

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

1NON-RELATIONAL DATABASE
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

2NON-RELATIONAL DATABASE
execution issues in the database server. If for this project, there is are two games is being
created by the same developers. Now if the developer are also associated with one game. In
this case, the games will have numerous developers as the values in the developer key. For
this situation the main conceivable technique is to embed the game developer components
inside game documents.
This adaptability of the document based No-Sql databases enables the users of the
information to match fields of any element as indicated by the decision of the client,
regardless of whether the information field is fluctuating considerably for various records. As
referenced beforehand the Documents put away in the databases can be signified utilizing
either reference or installed approaches between them.
The MongoDB likewise underpins dynamic queries on the put away documents in
created collection by utilizing document based query language which is as robust as SQL in
RDBMS. Moreover execution tuning, scale-out size of the database and mapping of various
application items to the database questions so as to recover the worth is not required for
mongodb. The server utilizes inward memory so as to store the working collection set which
aides in empowering quicker access to the information.
Other approaches
The referenced approach is another approach for document based database through
its theoretical model to create relationships, utilizing the abstraction and settling on the right
choices about the information storage. Providing a precise, unambiguous and concise design,
so database administrate-tors have significant gains in deliberation, understanding. Presenting
various sorts of connections between accumulations characterized as References and
embedded documents. Assisting the acknowledgment and plan of the objects, just as its
highlights and relationships with different items.

3NON-RELATIONAL DATABASE
Recommendations
A data item or document depicts a too many attributes which have their properties
managed in key-value structure. Information contained in a collection is denoted by identifier
(key) and the concerned value for the key. Different types of connections between documents
are characterized as References and Embedded relations with Documents Because NoSQL is
a non-relational database, the ideas of standardization, do not apply in this scenarios.
While working on the database, it is found that the mix of embedding and referencing
relationship creation technique can helps in the better performance of database. Embedding
and referencing can be merged with each other so that the complex queries can take small
amount of time for data retrieval. For example, consider a game in the given file, there is the
description information, the price which may change, and a list of supported device and
languages. All this complex relation between the attributes requires to embed some of them
to reference or some to embed in the documents. Merging of this two techniques are helpful
when the database contains too many complex relationships.