MariaDB Reviews

MariaDB is used like any other relational database where we need complex join queries as well as tasks like read and write using the tool. The tool also offers support in terms of sharding, which is why we use MariaDB. Every time we use the tool, we have some kind of a reason, or, I would say, a requirement of asset compliance, which is atomicity, consistency, isolation, and durability, which is only provided by a relational database. Companies usually go towards open-source databases. Oracle is very costly. Oracle is not an open-source tool, which is why people tend to go towards open-source. The databases are doing pretty well in different applications.

A well-known issue for a lot of different users is associated with write-intensive applications. There are so many write-intensive applications. Usually, the applications are designed as read-intensive ones, where the number of reads is way more than the write operations. I would say MariaDB or any other relational database is designed by default to be for read-intensive applications. There are a lot of features being added to the tool, such as something called Galera Cluster, which supports write-intensive applications and sharding. People have to come up with their own way to share their applications, and that is the only way they can come up with a better performance tool for write-intensive applications.

I have been using MariaDB for two years. I am not a customer of the product, but my company does cater to the needs of multiple customers. My company uses the tool at work, and it is a part of our product.

As a part of the NDA, I cannot discuss the number of users of the product since it is a public company, but I can say that we have thousands and thousands of customers, and every one of them has products that are on their own databases.

The technical side of the solution is there, and they have been doing this for a very long time. The solution's technical support team is responsive. I rate the technical support an eight out of ten.

Positive

I work with MariaDB and PostgreSQL.

The product's initial setup phase was not at all challenging, and the reason for that is there is so much community support. You could face any issues which are not properly discussed in the community. Almost every issue has been discussed in the community, so there is no way you could be stuck somewhere, and you are trying to figure out what you can do next since it will not happen when you use MariaDB.

The solution is deployed on a hybrid cloud model.

The community support offered by the product is good. There is one specific thing about community support, and it is that it doesn't matter if it is a relational database or any other code that is public and open source. If it is open-source, the tool gets enhanced multiple times in a better way because every company has its own requirements. As per the requirement, people are merging codes in the main branch, and I am specifically talking about GitHub for now. MariaDB has so much flexibility and features, like data compression, audit plugins, and tablespace encryption, and it supports discrete encryption. Because of the tool's community support, it has varied functions and can be used almost anywhere or wherever you want as a relational database.

In terms of data management efficiency, I would say that it is pretty efficient. The tool is simpler to support if you talk from an engineer's perspective, and it is easier to provide any assistance to the customer who needs some kind of data from their product. The tool provides its own high availability, which means a 99.99 percent high availability. The biggest thing about the tool is that it is an open-source product, and it is supported by a community, which is pretty nice, especially because the community improves the product pretty well. If the product was available at a certain price, there are very few requirements in such scenarios. For open-source products, there are multiple requirements, so the product is enhanced way faster, and that is why people prefer an open-source tool. MariaDB or MySQL are some of the most used relational databases.

It is not very complicated to maintain the tool.

I rate the tool an eight out of ten.

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.

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.

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 to process the data for the database, so it is just for storage and analytics-related areas.

The most valuable features of the solution stem from the fact that it is a cloud-based tool, so it is pretty fast. The product is also considered to be an SQL-compliant solution.

Document caching is an area of concern in the product, where improvements are required to help MariaDB improve on the previous queries as they are retained, and you can roll back to them.

A cloud-based tool that offers great speed with a need to improve in the area of document caching.

Stability-wise, I rate the solution a ten out of ten.

Scalability-wise, I rate the solution an eight out of ten.

Around 300 people in my company use the solution on a daily basis.

I rate the technical support a five out of ten.

Neutral

There was another solution in our company before MariaDB was introduced. My company moved to MariaDB as it was imposed or forced on us by the vendor named Appian since they prefer MariaDB for databases.

The product's initial setup phase was easy.

The solution is deployed on a public cloud by AWS.

The solution can be deployed in a few hours.

The product's setup phase was taken care of by a third party, Appian.

I have seen a return on investment from the use of the product since it helps my company save time.

I rate the product's price a three on a scale of one to ten, where one is low price, and ten is high price since there are some support costs involved, even though it isn't an open-source solution.

One person, who is the database administrator, is required to maintain the product.

I rate the overall solution a seven out of ten.

The solution is essentially an enterprise application. In our setup, there was a considerable amount of data being utilized. Later, the application shifted to the cloud, and for this cloud migration, we opted for a database switch from Oracle to MariaDB. That's why we migrated all the data and components to MariaDB.

The standout feature is the multitude of features available. There isn't a specific feature that's unavailable in other databases. The key differentiator is the speed. 

When referring to it as a hard code, the core size is crucial. In MariaDB, we can employ multi-processing, allowing users to make use of the core and process data more efficiently and swiftly.

In MariaDB, three aspects can be enhanced, starting with the indexes. Currently, the indexes are not as strong. The second area is related to exclusion queries, subqueries, or joins. There's one join that isn't fully supported, the product I came across about MariaDB.

Customer support can also be improved.

I have been using this solution for four years. 

There have been some issues. If you need to provide 24/7 availability, you have to follow the active-subprivate mode, where one application is active and the second is down. So, other substitute techniques, like mirroring and scrubber techniques, are also available for such scenarios.

It is a scalable solution. It easily scales up and scales down. 

The customer service and support are okay. But the response time is slow. 

Moreover, the material is not available freely.  

Neutral

We have used several databases like MySQL, Oracle, and NoSQL MongoDB. We have tried a number of solutions, so we have that experience.

We switched due to its features. It is a lightweight application, making it the best choice for our lightweight applications.

The initial setup is straightforward. It's not a big deal.

I have deployed it on the cloud, using Linux and everything.  It can be deployed within a day. 

When we were doing the technical evaluation, we considered MariaDB, Finsecure, and AWS cloud databases. Based on that, we made the decision.

Overall, I would rate the solution a five 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.

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.