I use the product as a backend to my application.

MySQL
JetwareExternal reviews
External reviews are not included in the AWS star rating for the product.
A stable and flexible product that is easy to use and can be deployed quickly
What is our primary use case?
What is most valuable?
The product is flexible and easy to use.
What needs improvement?
The interface could be improved.
For how long have I used the solution?
I have been using the solution for seven to ten years. I am using the latest version of the solution.
What do I think about the stability of the solution?
I rate the tool’s stability a nine out of ten. The stability is good.
What do I think about the scalability of the solution?
I rate the tool’s scalability a seven out of ten. We have four direct users and more than 1000 indirect users. We use the tool twice a week.
How was the initial setup?
I rate the ease of setup an eight out of ten. The deployment took a few minutes. We need two system administrators to maintain the tool.
What about the implementation team?
The deployment was done in-house. We need one system administrator to deploy the tool.
What's my experience with pricing, setup cost, and licensing?
I rate the pricing a seven or six out of ten on a scale of one to ten, where one is cheap and ten is expensive.
What other advice do I have?
We used different solutions before, but I do not know why we switched to MySQL. I recommend the solution to others. Overall, I rate the product an eight out of ten.
Which deployment model are you using for this solution?
Robust relational database management system offering flexibility and efficient data management for diverse applications
What is our primary use case?
We use it for building web applications and managing data.
How has it helped my organization?
It is quite efficient and performs well, especially when compared to MSCS. While traditional scaling methods can occasionally lead to slowdowns, I haven't encountered similar performance issues with MySQL scaling.
What is most valuable?
The installation process for the most scalable solution is remarkably quick, taking only a short amount of time. While restoration may theoretically take longer, I've achieved rapid setup with my system, often within a minute.
What needs improvement?
While utilizing a comparable algorithm, is noted to be sensitive, especially when configuring the inner device. If DCDR is not properly recovered from NDC, it can lead to system slowdowns. There is a need for enhancements in the InnoDB cluster, specifically the capability to support more than two nodes in MySQL. Additionally, the inclusion of data nodes would be a valuable improvement. For users new to the system, it might pose a bit of a learning curve.
For how long have I used the solution?
I have been working with it for one year.
What do I think about the stability of the solution?
I would rate its stability capabilities eight out of ten.
What do I think about the scalability of the solution?
I would rate the scalability eight out of ten.
How are customer service and support?
When facing support issues with your server, the level of assistance is generally high. However, in certain technical support instances, when issues are raised and a ticket is generated, the support team sometimes provides a link for further information. From a customer perspective, this approach is not ideal, especially when dealing with critical problems such as database downtimes. The expectation is for more direct and personalized support rather than reliance on knowledge-base resources in urgent situations.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I utilize Microsoft SQL Server (MSSQL) and MySQL for most of my databases. However, there are certain limitations in the new versions that impact support for certain functionalities. Due to these limitations, I have turned to MySQL as an alternative.
How was the initial setup?
The initial setup was straightforward. I would rate it eight out of ten.
What about the implementation team?
The deployment process, which took an hour, involves understanding various versions, especially the enterprise version, and confirming compatibility with the required features. Installation includes accessing the Oracle site, downloading MySQL, and dealing with complex considerations due to multiple business packages. Challenges may arise during the download of the DVD packet, requiring a careful assessment of the business needs for MySQL installation. The subsequent steps involve uploading MySQL VPN, reinstalling, and following a step-by-step approach, taking about five minutes. Despite the relatively swift deployment, managing dependencies and collecting necessary packets can be time-consuming and pose challenges for users. Maintenance requires only one person, especially if that person has knowledge of system administration. However, incorporating a software manager or other managing tools can be beneficial. Configuring and monitoring these tools doesn't necessarily require constant attention solely from the individual responsible for maintenance.
What's my experience with pricing, setup cost, and licensing?
It is an open source platform. While the free version of MySQL offers comprehensive features, it does come with limitations.
What other advice do I have?
Overall, I would rate it nine out of ten.
Which deployment model are you using for this solution?
Using MySQL for rest api software storage
First and best database
It has vast community of users and developers.
Best tool for data exploration and manipulation
2. MySQL is known for its excellent performance
3. MySQL is relatively easy to set up and manage
4.MySQL offers various security features to protect data, including encryption, user authentication, and role-based access control.
MySQL involves assessing features, performance, ease of use, and suitability for your specific needs
It's a very good Relational Database management service
It's open source.
Secure enough
Scalability on demand
Good efficiency
Server time
Comprehensive work flow control.
Select statements are not dynamic.
Sharing queries are difficult.
Dont have any debug tool