I think for what we use it for, mainly scheduling, forecast and to compare against payroll, it works well. I think there are some other things that could be added to it to use, like more expansive ways to use the forecasting tool and an easier way to pull previous data from prior years. This would help making the forecast for scheduling in the future.
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.
Security: is embedded at each level in MySQL. Authentication mechanisms are in place for configuring user access and even service account access to applications. MySQL is secure enough under the hood to store your sensitive information. Also, additional plugins are available that sit on top of MySQL for even tighter security.
Widely adopted: MySQL is used across the industry and is trusted the most. Therefore, if you face any problems, simply Google it and you shall land in plenty of forums. This is a great relief as when you are in a need of help, you can find it right in your browser.
Lightweight application: MySQL is not a heavy application. However, the data you store in the database can get heavy with time, but as in the configuration and MySql application files, those are not very heavy and can easily be installed on legacy systems as well.
This is an open source software so there are obvious drawbacks, the biggest of which is a lack of documentation.
MonetDB does not seem to be well known outside of the academic environment so there is less information when you are searching for answers of any type.
I'd like to see more use cases and/or best practices so that commercial companies like ours can optimally use all of its highly performant features.
The code is written in C/C++ and this can be negative if you are a mainly java-shop and need UDF - User Defined Function.
Although you can add the data you require as more and more data is added, the fixity of it becomes more critical.
As the demand, size, and use of the system increase, you may also need to change or acquire more equipment on your servers, although this is an internal inconvenience for the company.
For teaching Databases and SQL, I would definitely continue to use MySQL. It provides a good, solid foundation to learn about databases. Also to learn about the SQL language and how it works with the creation, insertion, deletion, updating, and manipulation of data, tables, and databases. This SQL language is a foundation and can be used to learn many other database related concepts.
I give MySQL a 9/10 overall because I really like it but I feel like there are a lot of tech people who would hate it if I gave it a 10/10. I've never had any problems with it or reached any of its limitations but I know a few people who have so I can't give it a 10/10 based on those complaints.
The support staff is friendly, knowledgeable, and efficient. I only had to get part way through my explanations before they had a solution. They will walk you through a fix or actually connect in and fix the problem for you--or would if you can allow it. I've done it both ways with them. They are always forthcoming with 'how to do this if it happens again' information. I love working with MySQL support.
There is a plethora of choices when it comes to NoSQL and columnar based databases. We use not one but sometimes 2 or 3 of them to carry out a specific purpose. We chose MonetDB because our engineering team enjoys working with open source software and appreciates its simplicity although becoming familiar with it did take time. I would not deploy MonetDB to production but it's a great backup option.
Each of the products has its own merits and demerits. however since MySQL is a very good documentation and global community its easy to learn and apply in different stages for analytics work. compare to other data bases its simple for setup and work on it. MySQL is cost effective and low risk choice for start up organization makes it more suitable for small to medium enterprises.
If you are familiar with a general database concept and played with open source products before then MonetDB will give you immediate return in terms of productivity since developers can quickly develop and verify their test cases involving back-end database with a large sample data set.
There is a stiff learning curve due to lack of documentation and sparse information available on the internet.
Overall experience has been positive since MonetDB gives you another option when it comes to building out a data warehouse.
