MariaDB Reviews

We're primarily using the solution for a data warehouse. It's just used to collect all this information from several databases, such as SQL Server, MySQL Server, DB2 Mainframe, and ZOS. We are collecting data from Excel spreadsheets. We're scanning and putting data right into MariaDB.

The best way to simplify our data governance process.

We like the easy way that we can collect data from other databases. 

The performance and the security that we got on it are great.

The way that they distribute the database is excellent.

It is a product that is very easy to use.

It's helped us a lot in our data governance procedure.

Technical support is great.

We'd like more data intelligence. We are working with a client who needs a lot of information about Oracle groups that come in the country, on the passenger name records, and so on. We need more intelligence around that in order to work better.

I've been using the solution for six months.

We didn't have any bugs yet. The solution is stable and reliable. We haven't had any issues yet.

We're still testing the solution with 30 people. Once we go into production, we'll train the whole company. therefore, we do plan to increase usage. 

We're quite happy with the technical support. We are satisfied as they are responding in time. They are giving us good answers. 

We did not previously use a different solution. We started with this product from scratch. We're still organizing our approaches to be more competitive.

We are implementing this solution with a variety of other solutions and setting everything up at once.

The solution is not so complex in that we don't want to resell any solution that we are not trying on ourselves. Therefore, we have a good understanding of how everything works, having done it ourselves.

We are still in production, and, after six months, we will begin deploying the solution.

On our side, we have three people working with MariaDB and two people at MariaDB helping as well.

We're working with our client's technical services to get everything deployed.

We don't have clarity on an ROI yet. We've just started using the solution. 

I can't speak to the exact pricing.

The cost of licensing is dependent on the projects. We have many types of licensing. We have a subscription and we also have some like lesson sheets that we buy. After, we just pay for the maintenance.

We evaluated many options. We went for simple software. We took Hadoop with Cloudera since the best version of Hadoop is Cloudera. Then, we have MariaDB on our HCI environment to secure all of this. There's a general sense of happiness with these products. It's really easy for us to use everything. Still, we are just at the beginning of the use phase.

We've started from scratch and we are using this product to build up use cases. 

We are a service company and we reselling the solution. We are working directly with MariaDB.

The product is easy to use. When you're a database administrator and you're working with databases, such as MariaDB, it's very, very, very easy. You get the performance, you get the security, and you get monitoring and disaster recovery. You're working in a secure area with the performance you need and can mass scale it which is very useful.

I'd rate the solution eight out of ten. We still are exploring all of the possibilities, however. 

I use MariaDB since my organization has different customers who use different databases. My company caters to the customers' needs depending on the database they want to use.

The most valuable feature of the solution is a relational database, which is fairly reliable. My company is satisfied with most of the features of the solution. My company just provides services to customers depending on what they want, so we don't necessarily dig too deeply into why they want it. If a customer asks for a referral or suggestions for a free database, then my company normally tries to push PostgreSQL, a tool we get directly from the vendor.

My company hasn't seen any problems with the solution where it has been running. The solution works fine for the purpose it is meant for, so there are no issues.

MariaDB should provide HA and archive logging. If HA and archive logging are present in the solution, it is hard to find them. The aforementioned details related to HA and archive logging need to be considered for improvement. I haven't had the opportunity to use the features provided by the solution since I don't know how to see them.

I have been using MariaDB for a couple of years. My company operates as a consultant offering support for the solution.

It is a stable solution. I haven't seen any stability issues for the purpose MariaDB is meant to function.

In my company, the instance related to MariaDB is fairly small, so I can't comment much on its scalability.

For MariaDB, my company has only one customer who uses it for a single instance, which is about 20 GB of data at the moment.

I haven't had the need to contact the solution's technical support.

The solution is deployed on an on-premises model.

MariaDB can be deployed in a day.

My company uses the free version of the solution.

With PostgreSQL, it's simply the archive logging functionality and remote hard clustering capabilities.

My company is not familiar with how the functionalities of PostgreSQL would work for MariaDB or MySQL.

I would tell those planning to use the solution that it is pretty much the same as MySQL, but since my company has dealt with only one instance in MariaDB, I can't say much about it.

I rate the overall solution an eight out of ten.

We are not using MariaDB alone, it is being used with other applications such as ServiceNow.

We are focusing on the underlying database of ServiceNow. 

We provide our customers with complete solutions that include implementation, support, and training.

Currently, our customers are on-premises and they have not yet considered this solution for on cloud deployment.

This solution is user-friendly. It's easy, and similar to MySQL.

Some areas where this product could be improved are in the clustering technologies, redundancy, active-active deployment model, and also monitoring the backup and restore solution to the cloud.

They have made some enhancements on the product but I think that scalability and redundancies are a concern for the entire team. In the next release, I would like to see improvements in the scalability and redundancy features.

This solution is stable.

This solution is scalable.

It is not suitable for mission-critical applications, but it is stable for other applications.

We had a customer who was fronting MariaDB with ServiceNow and we were not able to help her with a specific situation. We contacted customer service technical support and they were very good. They were able to solve our issue in a short time.

The initial setup is easy and straightforward.

The deployment took a day.

We are resellers but we are willing to be partners with MariaDB.

Before starting with the implementation and deployment you should read the guide.

You should look at the suggested tips, tricks, clues, and the requirements to avoid having any problems.

I would rate this solution a nine out of ten.

I installed the solution here in the company when they required MySQL. I tried MariaDB instead, and it works fine due to the fact that MariaDB is an exact clone of some parts of MySQL. It also has a database for a help desk solution, called a GPLI.

It's open source. It's freeware. It's very similar to MySQL. MySQL is a very good database management system, a relational database management system. However, the problem, or the potential problem with MySQL, is that it is under Oracle's umbrella, and I want to be prepared in case it's being commercialized and closed.

MariaDB was created by the same creator of MySQL. However, before he sold it to, at that time, Sun Microsystems, it was later acquired by Oracle. It's the same creators. It's the same programmer. That's what I like.

It's a one-time installation and configuration, and then I almost forgot about it. What I like is that it's very easy to configure, and just from time to time, you can make your backups, and that's it.

I don’t have any particular issue with the solution. It works well for my purposes.

I’m not sure if it can scale, so I’m not sure how it would fare for significant companies. I know that MariaDB has a cluster solution that I don't need at the moment. Probably, it would be a good idea to have a way just to confirm that the cluster is available for when I require scaling.

We’ve been using the solution for one year.

It’s quite stable. I haven’t had issues with bugs or glitches. It doesn’t crash or freeze. It’s reliable. It’s very similar to MySQL.

I’m not sure if it is scalable. Scalability doesn’t affect me as I am only using one application. I don’t require any scaling capabilities.

Indirectly through the help desk solution, the whole company has about 60 plus users on this product.

It's open source and freeware. The support that I receive is in the forums and the blocks in the internal information. You can’t call or email someone at MariaDB.

We also use SQL Server Express, MySQL Fork, and SQLite.

The setup is simple. It’s as easy as setting up MySQL.

This product is open-source and free to use.

I am just a customer and an end-user.

I'm not sure right now which version we are on.

Whether or not this is a good solution for a user depends on usage. You need to be sure that this is the solution for you. I'm not going to scale up, which is why it's my current solution. If I had to scale, I’m unsure if this would fit.

I’d rate the solution nine out of ten.

Our software development team uses MariaDB and other databases as the storage facility for some of our applications.

Initially, we liked this solution because it is a drop-in replacement for MySQL.

The most valuable feature is that it uses multiple cores, which is better than some of the other databases. When we have eight or sixteen cores, the utilization ratio is a bit higher than previous versions of MySQL. I think perhaps the enterprise version of MySQL may have better support, but the free version does not work as well as MariaDB. This is with the factory default settings.

Scalability is an area that needs to be improved.

When we have had issues with accidental computer shutdown or a power outage, our MariaDB database was corrupted. This did not happen with our Oracle or Microsoft SQL Server, so I think that there might be some differences in the database engine that better deals with these kinds of accidents.

We have been working with MariaDB for seven years, since 2013.

We have not experienced much in terms of instability. We have been running our instance since 2013 and it needs almost no maintenance. You just install it and forget it. It's that easy.

MariaDB works with just a little configuration for a small dataset, but it does not scale as well as Oracle of Microsoft SQL Server in our applications. For example, additional manual configuration or tweaks are needed so that a query will return in a reasonable time when there is a high volume of records.

Our client has between 10 and 30 concurrent users.

Getting proper support is sometimes difficult because when you have a technical issue and use Google to try and find a solution, there will be millions of results. You have to tackle it by yourself but even if there is the same error message, you can try every posted solution and it still might not work. There is not a single source of truth that you can rely on.

The initial setup is straightforward and I think that the installation can be completed in a couple of minutes.

We have our own team for deployment and maintenance.

I think that for a small team of fewer than ten people, such as a couple of developers, MariaDB is a very easy start. When the team size grows or when the complexity of the application grows, you might need to try other options such as Ingres or MySQL. In our case, at the very beginning, MariaDB covered almost every technical requirement for releasing version one of our application.

It is definitely a good start. Once the product has grown to a point where the developers know in which aspect MariaDB does not fulfill the requirements, then it's time to find a better match.

At this point, I cannot think of any additional features that I would like to see because most of what I want is already on the roadmap. I think that they plan to implement them one by one.

I would rate this solution an eight out of ten.

I develop applications in my spare time. So, if the application requires a database, I use MariaDB by default.

It works fine. It's easy to set up. 

There is room for improvement in terms of security. 

I have been using MariaDB since 2016. I started using it when I was in school. Moreover, I use the latest version available, depending on what I am doing.

It is a very stable solution. I made a deployment for an internal IT service at one of the places I worked, and it's been seven years now, and it's still working perfectly. 

I would rate the stability a solid nine out of ten. There is always room for improvement. Nothing is perfect, and maybe there are some issues that I'm not aware of.

MariaDB is mainly a back-end application, so anyone using our service also uses the database. For example, if you use my monitoring service, which is used to monitor devices and appliances, then you'll be using the database. So, I'm not sure if that counts, but it's being extensively used in our company, and it's very helpful.

We plan to increase our usage of MariaDB in the future.

I have never contacted the customer service and support team because our deployment is not very big; it's just something small. The data contained in it is not considered a big deal by my supervisor, so there hasn't been a need to contact tech support.

Moreover, we haven't faced any issues so far. It's been working smoothly for us.

The initial setup is very straightforward. Mostly, I use MariaDB with Docker, so it's quite easy to set up and deploy. The documentation is also easy to understand and follow.

I usually handle the deployment myself, without the need for any third-party help. I followed the documentation and steps provided. MariaDB can be deployed in-house, but mostly it's self-hosted, and I use it with Linux. I mostly use the package manager version or the bundle I get from the website and apply it myself. 

I haven't used the licensing model for MariaDB, but I would prefer to use it since I am familiar with the platform and find it easy to work with. I wouldn't want to switch to a different database management system.

I've used PostgreSQL before, but that was in a personal capacity just for my own personal projects. Using MariaDB depends on the application I'm trying to deploy or what I'm trying to use. That's what determines if I will use MariaDB or Postgres as SQL.

If I am teaching somebody to program and write applications, I usually use MariaDB by default because it's open source, pretty available, and overall, I would rate MariaDB a ten out of ten.

But if I want to do a major deployment, I would have to get support. It's very stable. For example, I was using it to host a monitoring system, and it's been stable for a very long time. I haven't upgraded it yet, but it's working fine. It's been seven years since I did the last deployment, and it's still fine. 

We use MariaDB for any instance where we need faster retrieval and processing rates, such as establishing relationships between data entities through entity relationship mapping. MariaDB is our preference for structured data, like user details or product information. However, for handling non-structured data, such as metadata, we prefer DynamoDB or MongoDB.

MariaDB is inherently faster than MySQL database. However, given the opportunity, our team would have likely chosen Postgres for better performance in terms of concurrency, etc.

MariaDB is likely less resource-intensive than Postgres and other RDMS solutions because it offers only a subset of features.

Concurrency is a challenge in MariaDB.

I have been using MariaDB for a year.

Ten engineers are using this solution.

It's open source, but there are no dedicated technical support resources.

The deployment should be easier because we use AWS EC2 instances to run and deploy the image and the services. It took a few hours to complete.

It's an open-source solution that only charges for a server database.

I rate the solution's pricing an eight or nine out of ten, where one is expensive, and ten is cheap.

A few EC2 instances are running that solve the MySQL and the service. 

Cross-functional GUIs are currently available. For example, we use DB Workbench, a solution that provides a GUI interface for MySQL, PostgreSQL, MariaDB, and several other databases.

It is seamless unless we want more advanced features, like simple database charting or event scheduling, which MariaDB doesn't support.

Our security team and platform team maintain security features. So, it depends on the type of protocols they use.

There are no particular challenges because the development kit, such as all the SD cases that are DB connectors, is well supported by Python and Java.

Our AI projects' data comes from non-relational sources like Mongo and Dynamo. Therefore, there's no direct correlation. However, MariaDB merely serves as a repository for information, such as profile data or some form of structured text (NTT), which can be displayed in tables or otherwise.

It depends on whether they prioritize performance and features. If so, they might prefer Postgres. However, MariaDB could be the better choice if they prioritize a time-tested solution and lower costs.

MariaDB offers more features than its competitors. It supports features like sharding and concurrent connections.

Overall, I rate the solution an eight out of ten.

I use MariaDB in my company for the deployment of web applications. MariaDB serves as a database software for web applications.

The most valuable features of the solution are that it is very stable and reliable. I like the fact that MariaDB is an open-source product and not resource-intensive. MariaDB runs on most of the operating systems of Linux. MariaDB is a cross-platform product, making it a great database choice.

MariaDB is a bit technical product, so whoever uses it will have to read a lot of documentation, which I don't think is a disadvantage of the product as it is just its nature. I believe that open-source products, in general, are a bit more advanced than regular systems. The difficult part related to the product stems not from the tool itself but is related to learning how to implement the product in the right way without creating any wrong configuration that could cause security issues or performance issues.

I have been using MariaDB for five years.

It is an absolutely stable solution.

It is a scalable solution.

Two or three people in my company use MariaDB.

I never had the need to contact the technical support team of MariaDB. I would usually find MariaDB's documentation and details online to read about how to deal with issues. Usually, issues in MariaDB are related to configurations more than stability as long as you make sure you install or use the stable version, which is considered to be a long-term supported system.

I moved from MySQL to MariaDB. MySQL is less maintained compared to MariaDB. Feature-wise and stability-wise, MariaDB is way better than MySQL from Oracle.

The deployment process of MariaDB is easy, provided you go through its documentation.

The solution can be deployed in ten to fifteen minutes.

Users can take care of the deployment part of the product by themselves, though, at times, it may depend on the project size that you plan to support with the software. If a project demands software that offers scalability and very high availability, the deployment process may take an entire day with many experienced engineers. If the deployment process is carried out for a single small system, it takes around fifteen to thirty minutes.

The solution is deployed on both the cloud and on-premises.

Quarterly maintenance is required for the solution. When some security incidents occur, the solution's maintenance may be required. If a security issue related to the system is revealed online, it would need immediate maintenance. Maintenance is required depending on the updates provided by the product, which usually occurs once a month or once a quarter.

One person in the company can take care of the maintenance phase of the product.

I rate the overall product a nine out of ten.