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.

MySQL
JetwareExternal reviews
External reviews are not included in the AWS star rating for the product.
The performance is optimal, the speed is very good, and there are no delays in fetching data
What is our primary use case?
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
We have been using the solution for projects running for the past five years.
What do I think about the scalability of the solution?
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.
How was the initial setup?
Most of our projects are on the cloud. A very small number are on the client's premises.
What was our ROI?
We are continuing to use the tool because it's been cost-effective. It's producing revenue for us. It's a beneficial solution.
What's my experience with pricing, setup cost, and licensing?
The tool is open source. We choose open-source software mostly. We integrate a very limited number of licensed software.
What other advice do I have?
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.
Provides good indexing and supports multiple data types, but performance needs to be improved
What is most valuable?
I would use MySQL for a medium project, with around 1,00,000 hundred thousand users, because of the indexing and stored procedures.
What needs improvement?
MySQL's performance needs to be improved for enterprise-level applications compared to Oracle and Postgres. That's the only drawback I found in MySQL. When the table storage is full, the solution's performance becomes slow. The solution's security needs improvement as DB2 is more secure than MySQL.
For how long have I used the solution?
I have been using MySQL for more than ten years.
What do I think about the stability of the solution?
MySQL has good stability.
I rate the solution a six or seven out of ten for stability.
What do I think about the scalability of the solution?
Around 150 users are using the solution daily in our organization.
I rate the solution a six out of ten for scalability.
Which solution did I use previously and why did I switch?
We previously used Oracle. We switched to MySQL because Oracle's license was costly.
How was the initial setup?
It's really easy to set up MySQL. On a scale from one to ten, where one is difficult and ten is easy, I rate the solution's initial setup an eight out of ten.
What about the implementation team?
We implemented the solution in our organization through a consultant. It took a few hours to set up everything. Around one to two people were needed to deploy the solution.
What's my experience with pricing, setup cost, and licensing?
MySQL is a cheap solution.
What other advice do I have?
When you compare Oracle and DB2 with SQL Server and MySQL, all these come under RDBMS (Relational Database Management System). Since the licensing for Oracle and DB2 is costly, people will go for either MySQL or Postgres. People go for MySQL because it is better than Postgres in indexing and supports multiple data types compared to Postgres.
Just one person is needed to maintain MySQL. We didn't face any challenges using MySQL because of many open communities. If you have MySQL's commercial license, you will get good support. I would recommend MySQL to users who are going for medium enterprise applications.
Overall, I rate the solution a seven out of ten.
Which deployment model are you using for this solution?
Best Open Source Database System
Enables a wide range of features and benefits, including high performance, scalability and security
What is our primary use case?
We use it to meet the requirements of our customers while optimizing performance and reliability within the constraints provided.
How has it helped my organization?
The performance and scalability of our project have been influenced positively by MySQL. From what I've observed, performance has been satisfactory, and I haven't received any complaints from teams that have implemented it.
What is most valuable?
While MySQL offers strong basic functionality.
What needs improvement?
MySQL lacks a feature akin to Oracle's Real Application Clusters, which ensures continuous database availability within the same data center or nearby data centers. Without this capability, MySQL's suitability for mission-critical applications is diminished. Until MySQL incorporates a similar feature at the application level, its appeal for high availability remains limited. Historically, we've relied on external security measures for data protection, such as encryption. However, when encryption methodologies are employed within MySQL, there may be a slight performance degradation due to the computational overhead associated with processing large volumes of data in the database.
For how long have I used the solution?
I have been working with it for twelve years.
What do I think about the stability of the solution?
Stability is crucial, and it's influenced not just by the inherent features of the database system, but also by how the application team writes queries. If queries are poorly written or not optimized, it can affect stability significantly. While logging can help, improper usage, such as logging entire tables instead of specific fields, can also impact stability. Therefore, ensuring stability requires a holistic approach that considers both the database infrastructure and how the application interacts with it.
What do I think about the scalability of the solution?
Scalability is not as straightforward with MySQL compared to Oracle. I would rate it seven out of ten. Our clientele typically includes small, medium, and enterprise-level businesses.
How was the initial setup?
The initial setup was straightforward. I would rate it nine out of ten.
What about the implementation team?
For the MySQL installation, it's crucial to have a broader understanding of the solution we're implementing. Sometimes, we may need to address OS-level issues, especially when dealing with OS-level addressing like OSFlow. In such cases, thorough testing at the voice level is essential to ensure a smooth installation process. Implementing MySQL in a single-node setup may uncover additional challenges that need to be addressed.
Typically, our focus is on implementing the product rather than the database or operating system level. While I oversee infrastructure aspects, the implementation process is heavily influenced by the specific application being deployed. From setting up voice-level deployment and alerting to handling licensing and the database infrastructure, this entire process usually takes four to six weeks, depending on the complexity of the functionality. Once we complete the initial deployment, subsequent enrollments become more streamlined, and the application is handed over for production use. Any further adjustments or configurations are managed separately.
What's my experience with pricing, setup cost, and licensing?
The pricing falls within the moderate range. I would rate it four out of ten.
What other advice do I have?
Rather than recommending specific servers or operating systems, decisions are driven by how the application behaves and what functionalities it requires. This approach streamlines the process as pre-tested systems are already available, reducing the time and investment required for testing. Overall, I would rate it eight out of ten.