MariaDB Reviews

In my work with ServiceNow, customer instances typically use MariaDB databases. As a performance engineer and tester, I focus on the application's performance and ensure its smooth integration with MariaDB. This means I'm responsible for identifying and troubleshooting any performance issues that might arise.

A relational database like MariaDB offers several advantages, including faster query execution and improved login security. Having evaluated other options like MySQL, I find MariaDB's strengths align perfectly with my specific database needs. 

MariaDB is known for its user-friendly interface and excels in specific performance areas. It delivers fast processing times, particularly for frequent select queries and insert/update operations.

While MariaDB is a good relational database, it can be inflexible for complex use cases. It doesn't adapt well to changing needs and lacks features like time series data support, which requires us to use ServiceNow's Clotho DB. In short, MariaDB's strength lies in its core functionality but it is not suitable for all situations.

While MariaDB itself doesn't offer built-in analytics tools, ServiceNow provides Stats Now for internal data visualization. This tool integrates with other analytics platforms like Splunk or Grafana, all pulling data from the same central source. MariaDB likely avoids including its own analytics due to these existing solutions within ServiceNow.

I have been using MariaDB for two years.

I would rate the stability of MariaDB eight out of ten. Certain queries can be slow but overall MariaDB is stable.

As a relational database, MariaDB inherits the advantages and disadvantages of this category, but it also offers easy scalability. We can add more nodes to the database cluster as needed to handle growing data and user demands. Additionally, MariaDB allows for the creation of backups to ensure data security and simplifies the scaling process itself.

MariaDB's initial deployment was smooth thanks to our extensive automation within ServiceNow. While data fetching hasn't been thoroughly tested yet, overall the process has been positive.

The deployment can take anywhere from one to seven days because MariaDB takes time to clone.

Between MariaDB and Oracle, I find Oracle is better because it provides a lot more information and is more comfortable to work with.

I would rate MariaDB eight out of ten.

MariaDB excels for well-defined tasks involving specific data sets. However, it might not be ideal for highly dynamic situations requiring frequent exploration and manipulation of large, diverse data volumes. 

I use MariaDB in my company to build simple web applications.

The most valuable feature of the solution is its interface, including the web interface and the CLI.

There is no guide provided to first-time users by the solution. For first-time users, there should be some sort of guide provided by the solution explaining what the product offers so that they don't have to search for it on Google. The very first time that users use the product, they should be able to use the database server and move it to phpMyAdmin.

MariaDB's GUI is an area with certain shortcomings where improvements are required.

I have been using MariaDB for more than a year.

I haven't faced any technical issues with the product, and it works fine. Suppose users have some other databases running in the environment apart from MariaDB. In that case, it might occupy the port that MariaDB's server is trying to use, so you might not be able to access it. There are no technical issues related to the solution unless there is another database in the same environment where MariaDB functions, making it an area where users must be careful.

The product has scalability features, but I haven't reached the level where I have to use them. If you know where to change the tool's configurations, it can scale up.

Though I still work with MariaDB, I have moved to Firebase and MySQL.

I have experience with some other tools in the past. The interface areas offered by other tools in the market are much better than the ones offered by MariaDB. The interface offered by MySQL databases is better than MariaDB's GUI.

The product's initial setup phase can be done straight out of the box, as it works fine.

The product's initial setup phase didn't require much time because MariaDB was already embedded within XAMPP, so it was easy to use and access since I only had to launch it. You may want to change the user credentials for the password before you can access it and use it from the CLI.

Price-wise, the product is affordable. The product is not expensive.

I rate the overall product an eight out of ten.

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.

It's a relational database, so it's mainly used for structured data. We use it for some of our in-house applications.

For us the benefit is that the system is very stable, so we don't have many outages. We also have a lot of experience with MariaDB, so we can optimally configure MariaDB and deploy a well-tuned environment.

I like the global transaction IDs (GTIDs) feature. It's quite reliable for replication between a master and a replica server, and it's a feature that MySQL also has but implemented differently. 

Another thing I like is the flashback feature, which allows you to roll back a transaction from the binary logs, so you can retrieve data. If someone deleted data, you can flash it back. That's a feature I really appreciate.

I'm interested in witnessing the integration of materialized views, which would enable the preservation of select queries. This particular functionality seems to be absent in MariaDB when compared to rival relational databases such as Oracle and SQL Server. The inclusion of this feature, akin to the offering from PostgreSQL, would be a valuable addition to MariaDB's capabilities.

I have nearly 13 years of experience working extensively with MySQL, and in recent years, I've also gained proficiency with MariaDB. Since MariaDB is closely related to MySQL, my combined experience with both platforms spans over a decade. Currently, we're utilizing version 10.4, although it's a few iterations behind the most recent release. We're actively preparing to undertake an upgrade in the near future.

It is a quite stable solution. 

If you want to scale it for larger use cases, like sharding, you'd need to consider MariaDB SkySQL or Xpand, which is a separate product designed for cloud deployments. So, for realistic scalability, especially in the cloud, you might need to use MariaDB SkySQL.

We have a couple of hundred users currently working with the database. It's probably around 400.

It's currently deployed on-premises, but we're planning to move it to the cloud in the future.

It's not difficult to maintain. It does require some maintenance, but it's very stable. You don't really need to intervene much, so it's quite stable. The main maintenance we do is patching and upgrading once a year. So it's not too taxing to maintain.

I have used MySQL or Oracle products. 

MariaDB, being open source, is a significant advantage, especially considering we use the enterprise edition. It's considerably much cheaper than Oracle, which is a proprietary database with high licensing costs. So, from a financial perspective, MariaDB is far more economical. 

Another advantage lies in its robust online community, simplifying troubleshooting and assistance. While we do have enterprise support, the online community and resources are quite valuable. 

As for cons, due to fewer contributors compared to other databases like MariaDB, certain features might experience slower development. Amazon and MariaDB Corporation are among the contributors, but it's an area that could use more attention. However, overall, MariaDB remains a strong choice.

MariaDB emerged as a distinct entity originating from MySQL, rather than being an inherent part of it. Formed in 2009 due to apprehensions that Oracle Corporation might negatively impact MySQL, which they acquired in 2010.

When deciding between MySQL and MariaDB, the feature disparity is minimal. MySQL has adeptly upheld compatibility since the transition, making it primarily a matter of personal preference. Some features differ between MariaDB and MySQL, catering to unique preferences.

In essence, MariaDB is a highly favored relational database, a commendable choice within the relational database realm. For those seeking a relational database, MariaDB stands as a solid option. As for purchasing a database, MariaDB comes highly recommended. It claims the second-highest rank globally and holds the second spot in the DB-Engines ranking. MongoDB ranks a bit lower, but the choice between the two is essentially equivalent.

On the whole, I would assign a rating of seven out of ten to this solution.

For various applications, we use MariaDB as a database to test the incoming and outgoing data for any application. 

We check the relational database, how it's working, how the data is organized, how the queries have been written, and how we can streamline or improve the performance of these stored procedures. 

These are the things we look for to maintain a good relationship between the front end and the back end of the system.

One of the great features of MariaDB is its scalability. It's easy to handle even with large databases. 

It's also user-friendly and allows you to create complex relationships with the data. It means you can fetch data from multiple correlated or related databases in a single query. So it allows complex relationships with specific databases.

MariaDB supports SQL, and it has an advantage over regular SQL in that it is a lighter version. Even with huge amounts of data, it performs well.

MariaDB is everything that SQL DB has, but it's much lighter and more flexible. It's also more expandable. So I don't think MariaDB has any disadvantages compared to SQL DB.

So the only issue is that it's not as lightweight as SQL DB. That's probably the only drawback.

In future releases, mainly the addition of security features would be beneficial for MariaDB. It would be great to have built-in capabilities that can be managed through plug-ins and system administration. This would require incorporating security measures into the code, which is a one-time activity but needs to be maintained. Wrappers can also be written for reusability and improved security. That's something MariaDB could benefit from.

Since I've been in my current company, we have used Microsoft SQL Server (MSSQL) as the database since the beginning. And then there's MariaDB.

Additionally, we also use Oracle in some specific projects.

Sometimes any system may have occasional issues, but overall, we are not facing significant problems. We used to face more issues in the early stages.

Overall, I would rate the stability a nine out of ten. 

MariaDB is quite easy to maintain. It's scalable and maintainable. Since it's Knox, directly or indirectly, around 40,000 people would be using it.

We have an in-house team to maintain MariaDB, so we don't require much external support.

I've worked with Oracle for one and a half years. Currently, I'm working with MariaDB and SQL DB.

I worked with Oracle DB before. Currently, I am not working with Oracle DB. Oracle is much more secure, but it is also costlier. 

With MariaDB, you have to be proactive. The security team and the design team need to be vigilant to ensure sufficient security measures. On the other hand, Oracle comes with security features included in the package, which is a major advantage. 

MariaDB is quite easy to install.

Deployment time depends on the level of application and the size of the database. For example, installing MariaDB from scratch may take some time due to design and architectural issues. 

However, if the DB is already available and you need to install it on your system, it doesn't take much time. It usually takes only one or two days, depending on the support you receive from the server side.

So, the number of people required for the deployment depends on the systems and the project. The magnitude of the database also plays a role. 

Since it's not a centralized database and specific to various systems, I would say for Knox, where we also use MariaDB in a large-scale system, there are more than 50 people involved in the design and database aspects out of a team of a thousand people.

And as for architects, there would be fewer. There are six to seven architects because there are different systems for nodes, meetings, Knox Mail, and Knox Client teams. So each specific system may have a dedicated architect.

MariaDB is relatively cheap. It is very cost-effective.

My advice would be, if you can handle the security aspect, MariaDB is a lightweight, scalable, and maintainable database that can be used for both small and large applications.

On a scale of one to ten, I would rate it nine. Due to its cost-effectiveness, scalability, and flexibility, I find it highly commendable.

We use several solutions for analyzing purposes including MariaDB, MongoDB, and PostgreSQL.

Our use cases for MariaDB are 50% for transferring data and 50% for storage purposes.

MariaDB is a user-friendly solution. Performance wise, it's better than SQL. With SQL, I would need to write a number of queries. In contrast, MariaDB is light.

In addition, MariaDB's transferring speed is very high compared to that of other DBs.

The dashboard and pricing need improvement.

I've been using this solution for one and a half years.

For stability, I would give MariaDB a rating of eight out of ten.

I would rate MariaDB's scalability at nine out of ten. We currently have 50 plus people using this solution including middle level software developers and data engineers.

MariaDB's technical support staff have been very helpful, and I would give them a rating of nine out of ten.

Positive

The initial setup is somewhat complex, but it can be overcome by reading the documentation and following it closely. The installation took about 50 minutes. The SQL development team handles the maintenance of the solution.

It is an open-source solution.

I would recommend MariaDB and rate it at eight on a scale from one to ten.

Around 90 percent of our clients are using MariaDB.

My company sells, implements, and supports ERP systems, and our particular ERP offering runs on MariaDB.

Our ERP solution runs on MariaDB by default. The second database that MariaDB also supports is not a tool we actively promote, but some of our clients prefer it and it is known as PostgreSQL.

The most valuable feature of the solution is the query speed it offers. It can really process queries, and essentially, every field that you add to a table is automatically indexed and can be queried.

The ability to create stored procedures in MariaDB is an area where the tool lacks a bit. It is an area where improvements are required. MariaDB is not as powerful as Microsoft SQL Server, which is a tool that I don't use because, in my opinion, putting a processing load on the database is not a good architecture.

I have been using MariaDB since 2018. My company has a partnership with MariaDB.

MariaDB is open-source and free to use. We do not need external support when we can support ourselves in terms of the technicalities surrounding its use or even help our clients who use it.

I actually use MariaDB, and I used PeerSpot's website to search for and compare the performance between MariaDB and MySQL for our company's marketing efforts. Now, we are pushing MariaDB in our company.

Over PostgreSQL, I can say MariaDB is comparatively easier to use. PostgreSQL is ideal for larger datasets as the processing works faster. The hardware requirements for PostgreSQL are slightly higher than those for MariaDB, which means our hosting services will incur more costs if we use it. MariaDB and PostgreSQL are more or less the same. PostgreSQL is slightly more scalable than MariaDB. There are some tech people who, because of even that small margin, even if they are really not going to be maximizing the power behind PostgreSQL fields, believe that it will work better for them.

My company helps the customers implement the product.

I have had no problems configuring the tool. There was one highly technical problem I had with it, but I have found a solution for it.

MariaDB is available for free.

In terms of AI or machine learning, we are actually developing predictive AI capabilities using MariaDB. Essentially, we have segmented our market into small, medium, and large. The data model we need for small is okay, so using MariaDB for small to medium businesses is fine. For large businesses, we prefer to go with MongoDB.

It is not my department to look into the AI part. We have our company's own AI labs, but it is not under my control. There are a couple of AI projects, but I am not completely aware of the details of the projects that my company's team is working on currently.

It can impact the operational costs of our customers compared to other databases. The tool obviously lowers the customer's total cost of ownership of the software because they don't need to pay a separate fee for the database.

My company doesn't offer that we don't charge separately for the database. It is really transparent to the end user to the client. When it comes to the cost of the database, it is free. We charge if our customers prefer it because it has a configurable option whether they want to keep the application server and the database server separate. If they want a separate database server, then we charge for the server but not for the database.

I recommend the tool to others. The main and primary reason why I even encountered PeerSpot website is to look for information and find data that will support my claim that MariaDB is as good or even better than some database solutions out there.

I rate the tool an eight or nine out of ten.

MariaDB provides a platform for developing our company's database.

The most valuable features of the solution stem from the fact that it is an open-source product and offers its users great online community support.

Sharding and the platform's vertical and horizontal extension and growth or scalability are areas with shortcomings that need improvement in MariaDB.

I have been using MariaDB for three years. I am a customer of the solution.

It is a very stable solution.

The solution is not scalable.

Around four people in my organization use the solution.

MariaDB is an open-source community software, meaning it is based on the generosity of others. I rate the technical support a six out of ten.

Neutral

The initial setup of MariaDB is easy.

The solution is deployed on an on-premises model.

Regarding the time taken to deploy MariaDB, I would say that in our company, we are still playing around with the platform. Our company is in the middle of a pivot right now, meaning we have plans to change our direction.

MariaDB is an open-source software, meaning I don't need to pay for the product.

I have no objections to the maintenance phase of MariaDB since I feel it is fine and easy.

I recommend the solution to those who plan to use it.

MariaDB is a community-supported product because of which I am not familiar with the paid support options that may be available.

I rate the overall solution an eight out of ten.

We use the solution for a certain database model. The application helps with recovery.

The solution is open source. The documentation is quite straightforward. It is a flexible database used in many cases, such as central bank systems, simple websites, and IoT projects.

Data continuity could be improved.

The stability is good, but we have received feedback from our review process that there are some weaknesses. For example, if MariaDB is running on our NOS Lake Red Hat and you perform an update, this can cause problems because the update may not be compatible with the OS. Therefore, it is important to keep MariaDB and the OS separate and to upgrade them separately.

The solution’s scalability is terrible. We need an office admin for the maintenance. We have around eighty to a hundred users using this solution.

The documentation is clear so there was no need to talk to technical support.

The initial setup is easy and takes less than an hour to complete. I installed MariaDB and set it up. They want it up and running, and I will give them the connection stream and everything else they need to keep the connection alive.

I recommend using the product. I have no specific advice and no complaints. If someone wants to use it, there’s no better way. Overall, I rate the solution a seven out of ten.

We use MariaDB for industrial automation. We log some tags, and we keep the tags in the database or historical storage.

It is very simple to install, and the commands are exactly the same as MySQL.

The learning curve is small and standardized, and not anything complicated. Other than that, it isn’t much different than other solutions. It's very similar to MySQL, but a little bit more light-weighted compared to it. Unless you do a very heavy login of data, it will be fine. It is based on AWS, and MariaDB is good for certain things. 

It should work across all fields like SQLite, as it is the basis of any application, even apps for phones and the like.

Usually, we are capable of handling our programs. We rarely use customer support. One time I got in touch with Oracle's customer service, but it was just one time. In general, we can handle the issues by ourselves. We are not really lower-level users and are all skilled with the programs. 

I have used PostgreSQL and Oracle. PostgreSQL and MariaDB are quite similar and we still use it.

The initial setup is very simple. The deployment was done within a few minutes.

I always use the free version.

I would rate MariaDB almost an eight out of ten.

I think it's a pretty useful database. It's very simple to install and that's one of the very positive things about it because sometimes if you go into tools like Oracle, it is more difficult. It is not just the downloading of the installer on any computer from Linux or Mac or Windows. MariaDB works in a blink of an eye, and the database runs right away.