Case Study Of Mysql Database

Chapter three: Case Study

In the previous chapter we generally mentioned Graph databases together with other types of NoSQL database; however, since one of the main goals of this thesis is giving a simple analysis for two systems, it is necessary to understand what main features and what these systems have. Consequently, in this chapter we will find what are the most Databases that have the best availability and scalability. First of all, we will choose a simplest type of the relational database and describe it which is MySQL. Secondly, will choose one type of the NoSQL database and try to analyze it and we will choose Neo4j which it is a graph database.

MySQL:

- MySQL server is one of the most widely used open source database management

Relational databases are the databases that divide the data into small chunk rather them putting them all together in one data source. The data is stored in tables which are referenced with other tables so that accessibility and flexibility is maximized.

- MySQL was originally designed to handle the requirement of large database faster and consistent than any other database. Keeping in mind the ease of use, security, connectivity, scalability and availability.

- ACID (Atomicity, consistency, isolation, and durability) are a group of principles that are controlling the relational model. MySQL is perfect for robust and easy interaction with the

The Data is replicated from the master node; due to the asynchronous nature of replication it will not guarantee that the data will be replicate from master node to all the slaves ' nodes immediately. Thus, this technique is useful based on the nature of the application.

- It follows the model of Master-Slave; it allows data to be replicated from MySQL database server (the master) to more MySQL database server (the slave). Any change in the Master will recorded into binary log like events. While each slave will receives a copy of the binary log and keeps read and execute the events. It means that it is a process allows maintaining multiple copies of MySQL data easily by get the data to copy automatically from a Master to a Slave database.

- Slaves need not be connected permanently to receive updates from the master. The slaves don 't need to be connected all the time to receive the updates from the master. That is mean the updates can happen through communications of long-distance, even through intermittent or temporary connections like dial-up