MySQL Review

Easy to use with a straightforward setup but requires better replication


What is our primary use case?

We primarily use the solution for the many small applications we use. However, we do not use it with our enterprise-level applications.

What is most valuable?

The solution is very simple. It's easy to use. That's the most important feature. 

We do have it supported by various programs we run with it.

What needs improvement?

The replication needs improvement. It's becoming a native cloud product like Oracle DB or Cockroach DB.

For how long have I used the solution?

We started using MySQL in various products about 10 years ago when it was still an independent community product.

What do I think about the stability of the solution?

The solution has proven to be quite stable. We haven't experienced any bugs or glitches.

What do I think about the scalability of the solution?

According to our experience, it's not really an enterprise tool that you can easily expand and scale the way you can with, for example, Oracle. It's good for small to medium-sized applications. It is not ideal for very big applications.

We have a data center that uses the application and it isn't very heavy on traffic. It basically runs on its own. We only use it occasionally. It's like a co-operation management system.

We do plan to increase usage, but we plan on looking at different databases. We're in the process of researching how scaling up would work. Chances are, we'll need to move to a different platform.

How are customer service and technical support?

We've never been in touch with technical support. For us, so far, things have been working perfectly so there hasn't been a need to.

Which solution did I use previously and why did I switch?

This is the first solution we've used. We don't use any other product. It's very popular with the in-house program, as we advised them to stick with this application.

How was the initial setup?

We've used the solution for ten years and the setup hasn't changed much over time. It is, more or less, simple when you compare it to other databases. 

Deployment takes less than an hour.

It only takes one person to maintain the solution. The individual doesn't have to be an engineer. They just need to be a support person.

What about the implementation team?

We don't need a consultant for the implementation. This is used by someone in our company that uses databases and has an average knowledge of the product. We don't even need a vendor. We can handle setup ourselves at this point. It's not like Oracle or other products that can be quite complicated.

What's my experience with pricing, setup cost, and licensing?

We use the community edition of the solution.

Which other solutions did I evaluate?

We didn't evaluate anything before choosing this solution. However, there are a few new products coming up that are growing in popularity and we will need to research them. Products like the Cockroach DB, Nuo DB, etc. are on our radar to be evaluated in the future.

What other advice do I have?

The most important thing other potential users need to do is to look at the use cases for this application and to evaluate how it's able to handle heavy loads, etc. Users should evaluate how it handles high-traffic. They'll need to ask themselves: is the solution usable for my applications? 

I'd rate the solution seven out of ten.

Which deployment model are you using for this solution?

On-premises
**Disclosure: I am a real user, and this review is based on my own experience and opinions.
More MySQL reviews from users
...who work at a University
...who compared it with Oracle Database
Add a Comment
Guest