MySQL

A thought on MySQL

Comments: As currently I have developed inventory system, clinic system, an backend application for a private company to manage huge no of memberships and ads, and a UK company for manage Business Name , Limited company, trademark and domain registrations and renewals. All of these used with mysql its those are running smoothly. Never had any headaches as through sql queries can manipulate easily and had fast responses for even complex queries and for huge no of data Frameworks used are spring boot and laravel.

Pros:

Known and used by most people as most secure and reliable relational database management system. Accompanies 99.99% uptime. Nothing to fears as open source. Can have millions of helps through community. Offers a wide scope of high accessibility like cluster servers master slave replication. Provides high performance even for large volume projects. Growing and improving frequently. Best for cloud applications and big data applications. Supports by huge no of frameworks.

Cons:

Red Hat Enterprise Linux, openSUSE, Fedora, Slackware Linux etc moved to MariaDB.

Great overall but has some very important caveats.

Comments: Mysql as any other tools has it's advantages and downsides.
It may be fast, ACID-compatible, it may serve as memory cache.
It has some dark corners and sometimes may hang on complex queries, or even corrupt the data (this is really rare case, but I faced it more than 10 times during my experience).
Consider your scenario carefully.
And always, always, ALWAYS make backups.

Pros:

There a whole world of documentation, best practice, books on mysql. It can be found on nearly any cloud, system, paas. It is really fast (on MyISAM), support transactions (InnoDB), may perform as in-memory cache (memory), or even CSV (never use this one except for testing or reports). Deploy and set up takes next to no time, it consumes very little resources. Actually I feel it is hard to write a review on MySql because over decades of extensive usage it become the standard de-facto, even LAMP has (M) for MySQL. It is a mature if, well known RDBMS with tons of extensions and forks (not sure I may name them here). It is worth to mention though that MySQL is a default backend storage for a whole number of software. MySQL is compliant to SQL standard though with some differences. It may require some changes to your codebase but still, they should not be critical. What will really surprise you is that ORDER by lacks "nulls first/last" clause and that collates may surprise you. In a somewhat unpleasant way. Window functions, virtual tables, temporary tables are here as well and trust me - this is quite important matter, something that is a vital part of any DB. You will find a lot of web and standalone management tools to work both with server and data, some of them are free, others are not, chose yours.

Cons:

First and biggest cons is that MySQL is not suitable for big amount of data. It always had and still have troubles performing complex joins. Database may get corrupted under some scenarios when significant selections is performed same time as other clients perform batches of inserts/updates (basically, there is a long lasting bug in memory management). Transactions are available in a single engine InnoDB and it is much slower than MyISAM. Worst thing is that in scenarios with multitenant databases with somewhat mediocre load MySQL starts to leak memory. This i a known well-issue, and there is no cure at this moment, you have to reboot the database instance. This is simply a disaster. Performance insight is something that could enjoy some more love. While Mysql is compatible with most of standard SQL, there are still some hard to explain differences.

Easy to learn and use - effective tool

Comments: Overall wonderful experience and great learning tool

Pros:

Very user friendly and easy to learn and connect

Cons:

Large datasets are not easily supported and may not be compatible

MySQL the default database server

Comments: We just use MySQL for all of our databases

Pros:

It's the default standard for many companies. MySQL has grown into a very stable product that never crashes. We've made the move to MariaDB, but found that the tables sometimes get corrupted when restarting a database server under heavy load. With the recent speed improvements to MySQL, we have decided to actually migrate back to MySQL.

Cons:

I'd really like if they would spend a bit more time on their CLI interface. As in, syntax highlighting in the CLI, an easier way to scroll through multiline queries when going through the history. I would also like it if we can specify a color scheme to use for the output.

Fantabulous Database Management Program

Pros:

Databases management in one place is what I like most about MySQL.

Cons:

It was quite daunting to deploy MySQL, but we acquired third-party system integrators.