External reviews are not included in the AWS star rating for the product.
Right now, I don't work very effectively with the tool. I am more like an architect currently, so I don't have to go deep into MySQL. In my company, we don't use Azure yet. Teamcenter PLM software is set up using Oracle or MySQL. We need to install Oracle or MySQL.
I used the tool for technical things for ten to twelve years. Right now, I have lost touch with how to use it.
The product is cost-effective, less expensive, and much faster, considering the way my company structures the data and the solution handled. The only thing is that if there are 10,000,000 or 20,000,000 records, it will slow down a bit. If the data is less, the performance is good. Once the data keeps on increasing, such as if we work with five terabytes of data and go up to nine terabytes of data, MySQL finds it difficult to handle the data. Huge amounts of data can only be managed by Oracle.
The performance issues in the product can be considered as an area where improvements are required.
I have experience with MySQL.
It is a stable solution. Stability-wise, I rate the solution a nine out of ten. Once the data increases, the tool will face some issues.
Scalability-wise, the product works very well. I rate the solution's scalability an eight out of ten.
My company usually deals with big companies having a minimum of around 2,000 people.
I have not contacted the product's support team since everything is available on the internet.
I used Dropbox when it was initially introduced. I had put so many documents into Dropbox, but I stopped using it. It has been a long time since I have used the product. I had used the product when it was launched, and the tool was giving two GB or three GB for free.
The product's initial setup phase is very easy. I rate the initial setup phase a nine to ten out of ten.
My company uses MySQL's corporate licenses.
In terms of our organization's data management strategy, especially if I talk about PLM software, which is about data management and can be regarded as the core data management of the products that we make. When we are designing something, specifically a new product, it is a critical area, especially considering that I am in the energy sector. In the energy sector, when we are building huge turbines and other things, the data might have intellectual property aspects attached to it. Even within the company, one region cannot see other regions to the extent to which the product offers security. In my company, we use PDM and PLM from Teamcenter effectively.
MySQL is not a tool my company uses in production. When we create some small demos, we use MySQL. For production, we would use only Oracle because it is the most stable tool in the market.
When we install Teamcenter, we don't need to touch the database. We just need to make some references to figure out this is the database, and it automatically creates everything. The basic thing about PDM and PLM systems is that the user should never touch the database because people may corrupt the data model or do anything that will have a very bad impact on the system. Database modifications only have to be made to the PLM system. We are not supposed to interact with the database directly.
The tool is very lightweight, less expensive, and sometimes it is free. It is a very usable tool that is preferred by a lot of people. Only for production use, I may ask people not to use it.
Integration of MySQL is like how we don't directly integrate PLM with Oracle. We have to use PLM's APIs to talk to the database. As a part of the best practices, we should not directly integrate anything with the PLM database. Feature-wise, the integration capabilities of the product are easy to use. It is like any other tool where if there is a table, there is a property. If you want to map a property using any middleware, then we can easily do that.
I recommend the product to others. For medium-sized companies, MySQL is one of the best solutions. Medium-sized companies can choose not to go for Oracle, which is very expensive.
In terms of the value or benefits derived by our company from the use of the product, I would say that it is not very expensive and provides performance along with scalability. The product can cater to the needs of customers ranging from 2,00,000 to 6,00,000 to 10,00,000 records. Even 20,00,000 records are fine, but after that, users may get into trouble. It is the best tool for mid-sized companies with a reasonable amount of data.
I rate the tool an eight out of ten.
We are developers working on different types of projects. We use relational databases in some projects and non-relational databases in others. When we use relational databases, we use MySQL. When we use non-relational databases, we use our DynamoDB or MongoDB.
Compared to some other database systems, MySQL may have limitations in terms of advanced features and functionalities, especially when it comes to complex data relationships and transactions.
I have been using MySQL for two years.
In my past two years of MySQL experience, I found no bugs or breakdowns. It works completely fine.
Many cloud providers offers managed mysql service with scalable architecture ,automated backups , monitoring and scaling. Leveraging this can solve the scalability problem.
MySQL is very easy to install and use.
As it is an open source and there is community edition available so if you have small or medium use case it is much cheaper to use.
Below are some thing to consider while working with mysql.
1. Regular maintenance
2. Security consideration
3. Version compatibility
You can try MySQL if you have any use cases of relational databases. It is very easy for somebody to learn to use MySQL for the first time. The solution worked fine for me, with no breakdowns or scalability issues.
Overall, I rate MySQL eight and a half or nine out of ten.
I use the solution for personal use cases like software development, mostly database bug systems.
I used the tool to build our website. It is used as a database to store information.
SKIP LOCKED is a valuable feature. It prevents us from deleting things we put in the database. It's mostly for background jobs in the software development site in MySQL 8. It is a new feature. The solution easily integrates with other tools and systems in our IT environment.
The full-text search feature must be improved.
I have been using the solution for the past three weeks.
I rate the tool’s stability an eight out of ten. We can create a database user schema. It's quite easy to update and remove in case anything happens. Backing up is quite easy. We have security features for the backup.
I’m the only user in my organization.
The product provides good documentation online.
It is easy to deploy the product. I deployed it on my own. The deployment took an hour. We deploy the product using Kamal. It uses Docker. The tool is deployed on the cloud. To deploy the solution, we just have to enter the password in the server and deploy it. It wasn't much of a hassle.
The tool is easy to manage and saves us time. It has much less complications.
We're using the community version. The tool is open source.
I also use PostgreSQL.
The tool helps us get the job done. It is not very complex. Overall, I rate the product a nine out of ten.
I don't use MySQL extensively, but I use the code within MySQL for preparing some reports and all that.
Code is easy to write and code, it's easy to understand. That's why it's widely used. The queries are very easy to understand and [write the] code. For coding, it's very easy.
The user interface could be more user friendly. Mainly because most of the times we see black and white digital lines. Something like Python.
I have been using it for three years. I have been using it since 2021.
I haven't experienced any bad things.
It is widely adopted in our company. We have around 60% of our total employees using it.
We have an internal support team. We usually connect to them, and they will resolve the issue. We don't need to connect to the MySQL team directly.
The initial setup is not very difficult. It's easy only.
The pricing is not much expensive, it's cheap only.
I would recommend it. For beginners, it is pretty much easier compared to other tools. The queries are very similar and easy to learn in a short span of time.
For beginners, it is very easy to use. It would be something easy to learn. It is a perfect tool for beginners.
Overall, I would rate the solution a seven out of ten.
MySQL is an open-source relational database management system used to store data.
MySQL is an easy-to-use solution that provides stability, reliability, flexibility, performance, security, and high availability.
MySQL could introduce more indexing strategies. There are a couple of strategies where you can index things to be more searchable and visible. We lack that kind of functionality. For example, if your name is indexed correctly with a certain strategy, it can improve the search results faster. The solution’s interface could be improved.
I have been using MySQL for my entire career.
MySQL is a stable solution.
MySQL is a scalable solution.
The solution’s initial setup is easy.
MySQL is a free and open-source solution.
MySQL is deployed on the cloud in our organization. Big companies like Netflix, Uber, and Facebook use the solution. Since MySQL is an old product, many people might have faced similar issues, posted them online, and got a resolution. MySQL's performance and scalability features have supported our database growth.
New users can follow the documentation to use the solution, as it is straightforward. You need to be very clear about why you want to use the solution. MySQL is a relational database management system that cannot be used as a dynamic database management system.
MySQL is generally faster and more efficient than other relational database management systems. Hence, it is our preferred choice for applications that require high performance.
Overall, I rate the solution a nine out of ten.
We use the tool in projects with customer records in the database. There will be a front-end application to search and find specific data from the tool. In another project, there are product listings, and the front end fetches data from the tool and shows it in a gallery or list view on the web page or mobile application.
We used MySQL in a project for a nonprofit museum. They have a lot of donors. They have a large repository of customers who give donations. They categorize the customers based on the money they give, such as steward level, platinum level, and diamond level. The client may send out an invite for an event for a certain group of customers, such as the patrons who donate the most. MySQL helped us in that project.
The optimized process is valuable. I have seen websites that take ages to load and show the data. Many web applications with lakhs and lakhs of data will take forever to show specific results. The database performance is optimal for the application we developed. The speed is very good. There were no delays in fetching data from the back end and showing it on the front end.
At times, the autoscaling does not happen when there is a surge in load. We had to depend on manual scaling. It led to website crashes in the past.
We have been using the solution for projects running for the past five years.
Scalability is one area in which we are very cost-sensitive. We always closely monitor the charges to increase the server scale. It will help us use more space in the DB if there is an economical way for us to pick up larger servers. We have more than six lakh end users.
Most of our projects are on the cloud. A very small number are on the client's premises.
We are continuing to use the tool because it's been cost-effective. It's producing revenue for us. It's a beneficial solution.
The tool is open source. We choose open-source software mostly. We integrate a very limited number of licensed software.
I have not seen any incident with a security violation or data breach. I have not contacted the technical support team. The infrastructure team contacts the technical support team regarding server-related issues. There is a LAMP stack. The Linux, Apache, MySQL, and PHP combination seems to be working well for enterprises' modern web applications.
Overall, the integration works well. However, initially, we worked with a third-party integration team to fix the APIs, query, and response code. Initially, some technical work will be needed. Once it is done, the integration turns seamless.
Overall, I rate the product an eight out of ten.