We changed our name from IT Central Station: Here's why
Get our free report covering Firebird, EnterpriseDB, MariaDB, and other competitors of PostgreSQL. Updated: January 2022.
564,322 professionals have used our research since 2012.

Read reviews of PostgreSQL alternatives and competitors

COO at a tech vendor with 1-10 employees
Real User
Top 20
Cost-effective, good performance, easy to use, and the cross-platform capabilities are nice
Pros and Cons
  • "What I've been most pleased with is the cost point, performance, and ease of use."
  • "The analytics features are in need of improvement."

What is our primary use case?

The primary use case is as a reporting solution, data collection, data manipulation, and similar tasks. We install MySQL on Linux and Windows machines for testing our enterprise application.

We are a solution provider and this product is part of our offering to our clients.

How has it helped my organization?

MySQL hasn't really affected our organization, specifically because we primarily use it in a consulting model.

What is most valuable?

All of the databases basically have the same set of features.

What I've been most pleased with is the cost point, performance, and ease of use.

It is very easy to configure, it's easy to deploy, and it's cross-platform capabilities are quite nice.

What needs improvement?

The analytics features are in need of improvement. They aren't as far along as the capabilities that you have in terms of analytics for SQL Server and Oracle.

For how long have I used the solution?

I have been using MySQL for about five years.

What do I think about the stability of the solution?

I've had no problems with stability and its recovery processing, error processing, and things along those lines have been fine.  We always use Java applications and the JDBC drivers work fine.

I haven't had any issues at all with its reporting or its transaction processing, or anything else. 

What do I think about the scalability of the solution?

For our use-cases, the scalability is fine. We haven't seen any issues and we're processing probably hundreds of millions of rows each day. We're not into the billions or tens of billions, so we're probably a medium-to-low use case.

Most of our instances are single-instance databases, so I haven't had to deal with its clustering capabilities or distributed database feature set.

Our clients vary in size, although we generally operate as a small system inside a major organization.

How are customer service and technical support?

I have never had to utilize technical support. There was never an issue that I had to call in.

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

I use a lot of databases including MySQL, Microsoft SQL Server, Oracle, and PostgreSQL. 

The performance of SQL Server and Oracle is better than MySQL. The two alternatives have other features, as well.

How was the initial setup?

The initial set up very straightforward. MySQL is easy to deploy and very easy to configure. We can literally bring up instances in minutes.

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

This product has a good price point.

Which other solutions did I evaluate?

We had been on SQL Server and Oracle, and a subset of our customers wanted us to switch and use MySQL. We explored what that transition would take and then implemented it.

What other advice do I have?

My advice for anybody who is looking into implementing MySQL is to start by carefully evaluating their use cases. One of the things that we found is that MySQL didn't necessarily have all of the flexibility for JSON and XML processing at the time. I know that they've improved it, although it's not quite the same as what you see specifically in Oracle. So, the customer has to evaluate that. For straight-on basic transaction processing, it's worked out just as well with few issues from SQL Server to MySQL or from Oracle to MySQL.

For my use, I'm fine with what they have. I'll be interested in what they'll provide in analytics, as well as JSON and XML processing if that's even on their roadmap. For right now, it's really not an impact on my use case.

If I were rating SQL Server or Oracle then I would rate either one a nine out of ten. The only difference is that they do perform better than MySQL, although they don't perform so much better than it's relevant.

I would rate this solution an eight 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.
Owner at TRS
Real User
Top 5
Works very well, easy to set up, and scalable
Pros and Cons
  • "We use MariaDB for identity provider services. Most of the things that we are doing are deployed in the container mode. All such solutions require a database, and MariaDB is easier to use for these kinds of deployments."
  • "It would be good if they can maybe improve the mass import in the database. Currently, for importing a large number of data, we create a CSV file and upload all the things in the system. The system does not activate them by default. We have to do this manually. This may be due to the version we are using, but this is something we would like to see improved."

What is our primary use case?

We are using MariaDB for our federation of identity system, which is used to record students, service providers, and many other things. This system uses MariaDB as a database. 

What is most valuable?

We use MariaDB for identity provider services. Most of the things that we are doing are deployed in the container mode. All such solutions require a database, and MariaDB is easier to use for these kinds of deployments.

What needs improvement?

It would be good if they can maybe improve the mass import in the database. Currently, for importing a large number of data, we create a CSV file and upload all the things in the system. The system does not activate them by default. We have to do this manually. This may be due to the version we are using, but this is something we would like to see improved.

For how long have I used the solution?

I have been using this solution for five years. 

What do I think about the stability of the solution?

It is stable. We have no issues.

What do I think about the scalability of the solution?

It is scalable. We are a regional research and education network. MariaDB is a part of the tools that we have deployed to provide services for such institutions. Three other national research and education institutes are also using it, and all of these institutions have many campus users. So, a large number of users are using it, but they don't even know that it is MariaDB because they are just using the tool or the application that has MariaDB as backend. We do plan to increase its usage in the future.

How are customer service and technical support?

We didn't contact them.

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

I won't say we switched because we still have another system running PostgreSQL. We started using MariaDB because we were using some tools for identity federation, and these tools come with MariaDB by default. We did not choose MariaDB as a standalone product. If we stop using any of these tools tomorrow, we may no longer use MariaDB.

How was the initial setup?

The initial setup is very simple because we are using a container, which means that it is just a deployment. It is a part of the installation of other applications. 

We didn't have to install MariaDB as a standalone product. We installed an identity management system, which automatically requires MariaDB, and all these things are done through containers. It is very easy these days when you are using a container. Everything is straightforward. It is just a matter of calling and installing them.

What about the implementation team?

The initial installation was done by a consultant. Since then, we have deployed many other instances of the same thing. It is the same container, and we keep on deploying it. We just change the configuration.

We have only one person for its deployment and maintenance. We have a network and system admin who deals with the installation for us. We are just using MariaDB behind our federation of identity system. So, we don't deal with it daily. When we want to connect a university or any university wants to join, we install the application that has MariaDB, and that's all.

What other advice do I have?

I would definitely recommend this solution. It has worked very well for us so far. I have no complaints about it.

I would rate MariaDB a nine 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.
Get our free report covering Firebird, EnterpriseDB, MariaDB, and other competitors of PostgreSQL. Updated: January 2022.
564,322 professionals have used our research since 2012.