Abstract
In this article we present a comparative study between the usage capabilities of MongoDB, a non-relational database, and MySQL’s usage capabilities, a relational database, as a back-end for an online platform. We will also present the advantages of using a non-relational database, namely MongoDB, compared to a relational database, namely MySQL, integrated in an online platform, which allows users to publish different articles, books, magazines and so on, and also gives them the possibility to share online their items with other people. Nowadays, most applications have thousands of users that perform operations simultaneously thus, it takes more than one operation to be executed at a time, to really see the differences between the two databases. This paper aims to highlight the differences between MySQL and MongoDB, integrated in an online platform, when various operations were executed in parallel by many users.
Highlights
Nowadays, an application must be accessible to its users 24 hours a day, 7 days a week, so it is important to implement an appropriate database, which supports simultaneous connection of hundreds of thousands of users [6]
To highlight the advantages of using a non-relational database, MongoDB, compared a relational database, MySQL, various operations were performed on the two databases in parallel by many users
This paper aims to highlight the differences between MySQL and MongoDB, using the databases described above, in a real application, where various operations were executed in parallel by many users
Summary
An application must be accessible to its users 24 hours a day, 7 days a week, so it is important to implement an appropriate database, which supports simultaneous connection of hundreds of thousands of users [6]. More and more complex requirements from users appeared, and companies were forced to find different solutions to meet the needs of their customers. The applications must support millions of users simultaneously and handle a huge volume of data and a relational database model has serious limitations when it has to handle that huge volume of data. Because each customer has his own needs and requirements, it might be possible that within the same application, there is a need for a different customization for each user. Relational databases do not allow a complete configuration that can shape after their needs. These limitations have led to the development of non-relational databases, commonly known as NoSQL (Not Only SQL) [11]. The NoSQL term was coined by Carlo Strozzi in 1998, and refers to non-relational databases, term which was later
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: International Journal of Advanced Computer Science and Applications
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
