Comprehensive Report on MongoDB: Implementation, Benefits, and Issues

This assignment provides a comprehensive overview of MongoDB, including its implementation using Studio 3T, benefits, and issues. The report details the implementation process with figures illustrating various queries and includes a table outlining attributes and data types. It further discusses the advantages of MongoDB, such as its schema-less nature, auto-sharding capabilities, and ease of use, while also addressing potential issues like reliability concerns, schema-less design challenges, and security vulnerabilities. The report concludes by emphasizing the practical and theoretical aspects covered, offering a valuable resource for understanding MongoDB database systems.

Introduction
The entire assignment is completed and based on MongoDB. The report consists of three
different sub-parts where each part is explained properly. The first part contains the entire
implementation of the assignment is shown that is done on Studio 3T using MongoDB. The
next part of the report contains the benefits as well as the issues of MongoDB. Each of the
attributes in the table along with their data types is also mentioned.

PART A
Figure 1: Query 1
Figure 2: Query 2

Figure 3: Query 3
Figure 4: Query 4
Figure 5: Query 5

Figure 6: Query 6
Figure 7: Query 7

Figure 8: Query 8
Figure 9: Query 9

Figure 10: Query 10
Query 11:
db.GameData.stats(1024 * 1024) { fileSizeBytes : 682428, avgObjSize : 0, }
Figure 11: Query 12
Figure 12: Query 13
TABLE:

ATTRIBUTES DATA TYPE
GameID Integer
Title String
Description String
Main Genre String
Genre 2 String
Genre 3 String
Genre 4 String
Game Centre Enabled String
Released Date Date (ISO)
Supported Device String
Context Advisory Rating String
Language 1 String
Language 2 String
Language 3 String
Language 4 String
Language 5 String
Language 6 String
Language 7 String
Language 8 String
File Size Bytes Integer
Mini OS Version Decimal
Developer ID Integer
Developer Name String
Developer URL String
Price Decimal
Currency String
Average User Rating Decimal
User Rating Count Integer
Current Version String
Current Release Date Date (ISO)
Current Notes String
Avg User Rating For Current Version Decimal

User Rating Count for the current version Integer
PART B
Benefits of Mongo DB
1. Mongo DB is basically schema-less document database in which one collection can have
different documents which might include number of fields, size as well as particulars of
that document can be included (Győrödi et al., 2015).
2. It can be used easily as it can do auto sharding which is basically storing of data in
multiple machines it could be used when there is less storage left in one machine which
we are using at that time to avoid such things sharding is used, this is generally done
when the machine is not able to store data sufficiently.
3. Using of Mongo DB is beneficial as single object structure is clear in it which makes it
more workable for new users to use it.
4. It is often used as it uses storage in the documented oriented format in a style which is
called as JSON style documents which can be defined as having no platform of writing
language i.e. it is language-independent, it was result of Java Script and used today as it is
very easy to use it.
5. There are no complex joints in it which makes it very easy to use it and it is not at all
complicated to use which means it could be worked out easily and can faster our work in
today’s fast pacing scenario.
6. It is easily scalable in nature that is it could be scaled up according to the growing needs
of the society which means it can survive for a longer time with growing population using
it, if it could not have done that then it is no means of doing marketing for it, as if it is not
done on according to growing needs than it is of no use of scaling it.

Issues of Mongo DB
There are many issues relating to Mongo DB which includes-
1. It is not much reliable to use it as one does not wait for any confirmation for every action,
they perform like they do not have to wait for any insert delete or update operation they
perform before starting the next action starts, this makes it faster but makes it more prone
to risks. They can allow rollback operation if any update fails but it is more prone to risks
in general.
2. There is also a problem with schema-less design as it is de-normalized it does not follow
a relational schema, everything is stored in JSON object which are called documents.it
allows it on the app rather than the database.
3. Mongo Db server is installed without a server which means that it invites trouble
evidently to them generally when one can do execution of random java script within a
query so this is prevailed issue of security of it which can be very harmful in general.
4. As its access is done through unauthorized user so it should always be kept up to date as it
is worth for checking logs for signs which can be counted as an issue for it as it is needed
to be updated regularly which is hectic in nature and time consuming too.
5. It fails to design a successful schema for it that it does not enforce a particular schema
which doesn’t means it doesn’t need it, as if this is done so then retrieval of the data
would be so difficult to perform which would lead to more time consuming and require
user to be engaged in it’s for a longer time (Haughian et al., 2016).
6. It can make a hell lot of data for storage that is it can store much required data at one
place but it doesn’t make any sense as it works evidently good only when it has a single
document and it is working in the single document only makes it easier to perform well.

Conclusion
The above created assignment is based on Mongodb database where the entire database is
being implemented and report also contains the large number of sub-types where different
theoretical as well as practical are being covered. The theoretical part covers the benefits
along with the issues in the report and also each of the attribute’s datatype is mentioned in the
report.

References
Győrödi, C., Győrödi, R., Pecherle, G. and Olah, A., 2015, June. A comparative study:
MongoDB vs. MySQL. In 2015 13th International Conference on Engineering of Modern
Electric Systems (EMES) (pp. 1-6). IEEE.
Haughian, G., Osman, R. and Knottenbelt, W.J., 2016, September. Benchmarking replication
in cassandra and mongodb nosql datastores. In International Conference on Database and
Expert Systems Applications (pp. 152-166). Springer, Cham.