MySQL

Our business requires keeping clearance records such as stock footage and music licenses, clearances and contracts with individuals, payments and contact information etc. It is called a production bible that can be referenced. An example is years after we completed work we will get a call asking where we got a photo and can it be used for another purpose.

Small footprint line of business apps with performance being the primary goal is the ideal scenario for running MySQL 8 in a corporate environment. It is well suited even for junior developers because it has a fairly simple learning curve and can be deployed into any environment regardless of the operating system or virtualization technology being used.

Mysql is Fantastic for:-
1. User Management
2. Transactional Data
3. Final Reporting Data as it can be very quickly accessed and displayed on graphs

Not to be used for:-- It cannot be horizontally scaled so not suitable for very high data volumes- Should not be used for storing unstructured data- Should not be used real-time analytics, content management, document intensive storage

If you are looking for a database management system which is easy to use then MySQL should be the number one choice without a doubt, however, if you are looking a platform to handle large datasets and complex queries then you might have to give it a thought.

From my own perspective and the tasks that I perform on a daily basis, MySQL is perfect. It has a reasonable footprint, is fast enough and offers the security and flexibility I need.

Everyone has their preferred applications and, no doubt, for larger data warehouses or more intensive applications, MySQL may have its limits, but for the area that I operate in, it's a great match.