Data Structure Comparison Between MySql Relational Database and Firebase Database NoSql on Mobile Based Tourist Tracking Application
I K G Sudiartha, I Nyoman Eddy Indrayana, I Wayan Suasnawa, S A Asri, Putu Wijaya Sunu
Abstract
Tracking application is widely used to help outdoor activities. One of them is used to help tourists who do tourist destinations in group activities. Tourist tracking application requires data on the position of tourists on earth. This coordinate data can be obtained using latitude and longitude data from GPS (Global Positioning System). Coordinate latitude and longitude position of tourists from time to time are stored in a database. Database Selection for media storage will determines the level of speed and ease in accessing data. There are some differences in designing the structure of the MySql and Firebase databases. Relational Database begins with identification of entities involved in the system. One entity with another entity is related and has a cardinality level of the relationship. Relational database implementation in the form of tables in normal forms that are interconnected. Data will be stored in columns and rows. Normalization of tables causes high query computation when calling data that involves many tables. Firebase, which is one of the NoSql databases, in building data structures is stored in JSON objects. JSON tree structures usually consider the display of information that will be presented to users. So that the generated JSON tree has high efficiency and speed in processing data. In this study a comparison between the design of the relational database structure, namely MySql and NoSql Firebase database structure was developed. Firebase is more power full for the development of applications which update data in realtime and and handle a lot of coordinate data such as tourist tracking applications. Applications that do not have complex data relations such as tourist tracking applications are more suitable to use firebase than using MySQL.