Which case should I use MySQL, which situation should not use MySQL? What should be paid attention to when running MySQL database? Let’s find the answers in this article.
Relational databases have been at the forefront of decades, and at that time, the choice was pretty obvious MySQL, Oracle or MS SQL. They are the basis for tons of enterprise applications, while modern applications require greater diversity and scalability.
What is MySQL?
SQL is used as the standard language for most RDBMS (Relational Database Management System) such as Oracle, Informix, Postgres, SQL Server, MySQL, MS Access, and Sybase. This database was originally built by MySQL AB and is currently owned by the Oracle Group. It uses structured query language (SQL) to access data and commands like ‘SELECT,’ ‘UPDATE,’ ‘INSERT’ and ‘DELETE’ to manage.
Relevant information may be stored in another table, but using JOIN operations allows you to correlate with it, perform queries on different schedules, and minimize the possibility of data duplication.
In the 1970s, SQL was developed by Raymond FF. Boyce and Donald D. Chamberline at IBM as SEQUEL. This phase, SQL is designed to manipulate and retrieve data stored in IBM database management systems. SQL was commercially deployed in June 1979 by Relational Software for VAX computers.
Things you should remember when operating this database system
MySQL is compatible with almost all operating systems, namely Windows, Linux, Unix, Apple, FreeBSD and many other operating systems. Sounds easy, but if you don’t understand the following issues, you may have trouble later.
Scaling is quite hard
In the first stage of release, the amount of data used on MySQL is small, the memory allocated for the cache is low so that it can push data up there.
But after a period of operation, the amount of data increased dramatically, the number of access of users also increased. As a result, the cache hit rate in MySQL will decrease (because there is not enough memory to store the cache). As a result, the computer must read data from the disk instead of from the cache, and this obviously causes the speed to drop.
Maintenance, failure over is quite large
When MySQL is being run under a master-slave mechanism. Unfortunately, for some reason, the master is down. Then MySQL will perform failover (move the down master to another backup master). This process will take a few minutes. With a business that requires strictly about downtimes (for example, a game project), perhaps with a few minutes of failover, it’s probably not acceptable.
Confidentiality and right to exploit information of users
Because of the advantages, MySQL can have many concurrent users, and it is necessary to have a secure mechanism to decentralize database mining. Multi-user or local operating systems must provide this mechanism.
The sovereignty of the data
This disadvantage manifests itself in terms of data security, the ability to express the semantic relationship of data and the accuracy of the data. Database users must update the database with the latest information. So it could lead to some problems with sovereignty.
When multiple people access the same database for different purposes, there is a potential for data contention. At this point, you need to have a priority mechanism when accessing the database. For example, the admin can always locate the database, and you can give priority to each miner.
Ensure data safety when something goes wrong
When the database is extensive and centralized, the risk of data loss will be very high. The leading causes are sudden power outages or storage devices failure. Currently, some operating systems have mechanisms to automatically back up the hard drive and fix errors when problems occur. However, keep in mind that ‘better safe than sorry,’ we should back up data in case something goes wrong.
Over the years, SQL has become one of the most widely used database languages in the world. It has become a standard for the International Standardization Organization and the National Stands Institute of the United States.
Actually, every database has its advantages and disadvantages. You should carefully study them before deciding to choose a database that best suits you.Hopefully, the above information can help you to make your decision when considering using these types of databases.