I use MySQL as middleware to get the extracted data from the database. I work with MySQL as an administrator to set up the whole platform. And I document the recipe for setting up the MySQL database.
We are working with the latest version.
I use MySQL as middleware to get the extracted data from the database. I work with MySQL as an administrator to set up the whole platform. And I document the recipe for setting up the MySQL database.
We are working with the latest version.
SQL is just a relational database. It is open source. It's pretty good. I have been using it for a long time.
Because I am the middleware guy I'm not the SQL database administrator. If I have any issue with it, I'm going to contact the right person. Sometimes, not because the version is not the latest version, there are some issues with it. Sometimes there's an issue with the server which creates issues with it. Then, when the administrator checks the status and makes notes, it works normally and the problem is fixed. With a big company you are not going to work directly with the MySQL database. We are the end user and not the administrator of the SQL database.
For MySQL, in terms of the usage or as the end user, I don't have much to recommend, as long as the query latency meets your requirements, it will be great. Otherwise, it's the horizontal scalability and you get more parallel in the implementation in terms of the SQL database regardless of the usage. This is probably much better than the vertical in terms of scalability.
I have been using MySQL this year.
If you are working in the cloud platform then you do have scalability because the cloud platform is usually AWS or GCP, and they provide this kind of scalability. If you get some issues with the query and latency or something like this, that is an issue of scalability and you can just adjust the horizontal or vertical scalability to meet your requirements.
But the company I was working with was a very big company. It's more than several thousand people and they usually have a lot of data that they are going to store in the MySQL database. They gather the data from the SQL database and then transfer it like ETL and you get data from all the different distributed systems and then put them into the centralized MySQL database. After that you're going to visualize this kind of data so that you can use the Power BI or that kind of tool to generate reports or to create a dashboard for the system. This company had its platform on-premises, but right now they are moving these technologies to cloud. That's why I'm talking about the scalability in two different ways cloud and on-prem.
For technical support, I'm the end user so I extract data or visualize the data from the SQL database. I didn't get too into the daily maintenance of the database.
The initial setup for the SQL database is not complex and it even integrates into the platform. You set up the recipe and then just follow the build book. Then it works as long as you follow the procedures.
Regarding the price, because it's the open source they have different licenses. Even for open source there's a license for the enterprise. I don't think it is expensive. Also for the scalability in the cloud, the price is based on the usage, such as, how much data you transfer.
For the best usage right now, the trend is to move the platform from on-premise to cloud. Then, you you really have the best flexibility to scale down or scale up based on your usage. You can make full use of the resources and then pay for whatever you use. Because if you have it on-premise you always pay the same price no matter how much usage you have. So one of my suggestions is if you plan to set up the platform for MySQL, it would be best to go directly to the cloud solution.
On a scale of one to ten, in terms of the usage for the middleware team and the end user of the SQL database, I would say it's around an eight at least. I cannot say from a database administration perspective.
To determine what would allow me to give it a 10, I would first have to get more experience using it on the cloud version.
Our main use case for MySQL is for applications and seamless migration to the DR site. And the application in this case is an airport application.
I can meet the RPO in almost real-time. This changes the customer experience. That testing still needs to happen, but that is one of the advantages of MySQL. We have found MySQL to be a very sturdy and strong database. And I have run it in a solution where it's almost real-time, so it runs very efficiently.
MySQL's clustering features are very strong, and you can automate scripting, so that helps. We wrote a Terraform script and ran it.
Rather than going in-depth about the technical features, which a technical person can directly tell, I would say that MySQL should be able to adapt to the next framework. The 5G framework means an unstructured framework. So if MySQL becomes smoother and more adaptable, it'll be easier. In terms of new features, automation is always the biggest demand from our customers.
I've been doing pre-sales and working with MySQL since 2007.
I would say that MySQL is definitely stable, but its scalability has yet to be tested. I cannot say right now.
We follow an agile strategy, so deployment is done in parallel. In comparison to other databases, I have always found MySQL to be the most efficiently managed. Of course, I don't discount Postgres, but MySQL deployment always has gone smoothly. I've never had an issue during migration, even on the granular level. UID numbers, which we commonly face in Microsoft SQL, have never been a problem with MySQL.
We use the implementation partners for OEM.
We get the standard packages, but mostly MySQL is freeware. You pay for a license to get the upgrades. We pay for an enterprise license if that is required, but that's not in every case. It depends.
I would rate MySQL nine out of 10.
We use MySQL to store data for our customers, in the database. It is a service-related application. Also to configure the data.
The fact that it is free is what appeals to me the most.
Scalability could be improved.
We use MySQL, which is a component of Oracle but operates as a separate database.
We have been using MySQL for more than ten years.
We are not using the most recent version, but rather one that has been tested with our applications.
We don't always use the latest version.
MySQL is a stable product.
It is very scalable. There are third-party solutions to assist with scaling but that may cost money, or it is available in the Commercial edition of MySQL.
We are primarily interested in Red Hat technology. As a result, we have primarily worked with Red Hat products.
This virtualization is built into Red Hat Hyperconverged Infrastructure.
We use both Red Hat Enterprise Linux, and Red Hat Hyperconverged Infrastructure.
The installation is straightforward.
We are using the free community edition of MySQL.
Definitely, I would recommend this solution to others.
I would rate MySQL a seven out of ten.
We use MySQL for internet applications.
MySQL is easy to integrate. It works with just about every language.
Security is a concern. MySQL could have better security features.
I've been using MySQL for several years.
I've never contacted technical support. It is done on the internet. You have all the support there.
Setting up MySQL is no problem at all. I can do it by myself, and it's deployed almost instantly.
I would rate MySQL nine out of 10.
We are basically using it for our applications.
I like the JSON stuff.
Since we upgraded from 8.0.12 to 8.0.22, it has had some slowness-related issues. Some of the queries that were fast previously are quite slow now. I did some research, and I found many people complaining about it.
I've been working with this for two and a half years, and they have been using it for 10 to 15 years.
We are using a cluster now, but I don't administrate that. There are thousands of users.
I would rate it a seven out of 10.
We use the solution for our applications, as a management system. We utilize it as an operator or relational database.
I am totally satisfied with MySQL. I like its performance, ease of use, stability and scalability.
The solution could have better integration and security features.
I have been using MySQL for more than five years.
The solution is stable.
The solution is scalable.
I have no experience with tech support.
We did not use another solution prior to the current one.
Installation is easy. It takes about 20 minutes.
One can do the installation on his own.
Our team involved 15 people.
There is no licensing fee.
I believe there are 100 users making use of the solution in our organization.
I would recommend this solution to others.
I do not recall which version I am using.
Although we do not use it for the main core system, the solution acts as a database which is useful for login applications, data warehousing.
The solution is so stable. I have encountered no problems.
The solution could be more secure.
I have been using MySQL for a year.
The solution is very stable.
The solution is not scalable at present.
I do not have experience with technical support.
Previously, we used Microsoft database.
The solution is easy to install.
I cannot state how long implementation took.
The solution does not come with a licensing fee.
I do not know the number of users who are using the solution in my organization.
I would absolutely recommend this solution to others.
I rate MySQL as a seven out of ten.
We primarily use the product for small applications.
The solution is great for small applications in particular.
The performance is good.
The solution originally was designed as an open-source product. It has a community edition that anyone can use for free.
The initial setup is simple and straightforward.
I have doubts about its overall stability. It's something that they should look at.
As an open-source product, there isn't really any technical support available if you get into trouble or have issues.
There isn't much scalability potential in the product.
I've been using the solution for a very long time. It's been years at this point.
The stability could be better. It's not as stable as I would prefer it to be.
It was originally designed as freeware, as an open-source project, and the community wrote the solution. However, they've made it worse over time.
That said, the performance is pretty good.
The solution is not that scalable. It's not something you should pick if you need something to expand significantly.
While I can't speak to how many people use the solution in our company, I can say that it is used by several departments and divisions.
The solution is open-source and managed by a community. Therefore, there is no technical support available to users.
The initial setup is very easy and quite straightforward. It's not overly difficult or complex.
That said, I was not a part of the original setup and therefore cannot speak to how long the deployment took my team.
We didn't need any assistance from integrators or consultants. The setup was handled in-house.
The solution is open-source and free to use. We have the community edition. We don't have to pay to use it right now.
Right now, Oracle has taken over the business of MySQL. Now, it's standard that you have to pay money for the license. That's why we are shifting all our databases, the small, small databases, from MySQL to Oracle. We do have extra data, so we do require a license.
Currently, we are using the previous version of the solution. I can't speak to the exact version number, however.
I'd rate the solution at a five out of ten.
I wouldn't recommend it to other organizations at this time.