We use MySQL and MariaDB for most part of our mission critical applications
This as it is so simple to integrate with web applications, and other well known applications.
We use MySQL and MariaDB for most part of our mission critical applications
This as it is so simple to integrate with web applications, and other well known applications.
Since it has many integrations to web applications, it is very easy to install and deploy open source web applications.
How it uses clustering.
The API's to PHP, ruby, perl, java, python, and many more high level programming languages makes it easy for us to deploy new features fast.
How to scale out with shard clusters.
The way how to handle replications needs to be improved, as we noticed that there are some performance drop of (using only one core for example)
No issues.
Yes, the binary log replication process in a cluster environment has issues processing data as fast as it arrives.
Customer Service:
A 10 out of 10.
Technical Support:
A 10 out of 10.
We have been using many different types of databases, and will most likely use this one for part of our systems, as it is has so much integration.
The initial setup was easy.
We implemented it in-house.
Free.
Be sure to take backups of the solution, as this will check that the blocks are okay.
We decided to use "DB Protection for MySQL" as it has options to perform block level incremental forever, and integrates well with Spectrum Protect.
Yes, we checked MongoDB, PostgreSQL and MariaDB.
It depends on the use and implementation, as I prefer to use Galera or XtraDB because of replication and failover functionality. However, the ability to scale horizontally is much better than other vendors. Also, the transactional functionality is good.
Configuration templates and reliability both need work.
I have been using MySQL for over five years.
I deploy multiples of these servers now, and it is all managed via a puppet so I/we have not had problems with deployment in a long time.
An overload of sessions, or long running queries. can cause the servers to be unusable.
Currently no, as we use our own load balancer to enable us to scale to any level.
We don't use it.
It was straightforward, and there are numerous blogs on-line that cover every possible configuration.
We did it in-house.
It takes about six months, but this does depend on its associated product and usage.
Chose your database based on traffic type and desired functionality, not on the initial cost.
If you have the in-house knowledge MySQL can be a great product. If you do not I would recommend using MSSQL instead.
Take a look at the environment you plan to implement including the application and traffic model.
MySQL is very flexible, has excellent performance, and it's simple to use.
Once we needed to use a database to distribute a product for my company and we chose MySQL, it was easy to use and it is very small, but powerful.
Maybe the way to build clusters needs to be improved. They could also improve the installation process.
I been using MySQL for nearly seven years.
There were no stability issues.
There were some scalability issues.
I would give the technical support an eight out of 10 rating.
We did upgrade the version with improvements to the product.
The setup was complex in the cluster installation.
MySQL is one of the best database options. The Community version is great.
We used Oracle and SQL Server, but their prices and licensing were so expensive.
Using MySQL could be an excellent option for you.
This product is valuable because it is used in production environments. Online backup can be implemented by activating a temporary storage similar to the Oracle's flash recovery area and introducing Percona innobackupex. This is possible from version 5.6.
It permits services such as data warehouse and retail.
The online backup needs to improve.
I have used this solution for 15 years.
We did encounter stability issues.
There were no scalability issues.
Not applicable because we don't purchase commercial support.
We switched due to cost saving reasons.
The setup was of medium-level complexity due to memory parameters.
Compared to PostgreSQL, it has an online backup feature only with the extension of Percona innobackupex.
We use this solution for billing, accounting, and data analysis.
The most valuable feature is the ease of use.
The manuals or documentation could be better.
I have been using MySQL for ten years.
We are using version 8.
We do not have any issues with the stability of MySQL.
For our needs, it's sufficient.
We have 10 users in our organization.
It has more than enough support available for our needs. There is plenty of support from the community.
We rely on the forums and other channels for help. It's pretty good at the moment.
The initial setup is straightforward.
The installation can take approximately an hour.
You need to be aware of databases to make use of it. You need a moderate level of competence.
We use the community edition.
There is no cost involved, no licensing fees.
We did not evaluate other products.
It's a good product for new startups.
I would rate MySQL a seven out of ten.
It is the database for a web application. I am using it for personal and official purposes.
It is easy to use.
It is not as powerful as SQL Server. It can be more powerful.
It is not scalable and has certain limitations, which is not the case with SQL Server.
I have been using this solution for a couple of years.
It is stable.
It is not scalable. We have around 10 to 15 web developers who are currently using it.
I have not interacted with them.
Its installation is not very complex. It takes two hours.
I installed it on my own. We have four or five people for deployment and maintenance.
For the on-premise version, no license is required.
We plan to keep using this solution. I would rate MySQL a seven out of ten.
Nice detailed explanation regarding advantages and disadvantages of MySQL. I agree with author on various points like popular free opensource database. But it doesn't support PL fully.