MariaDB Reviews

The tech stack we commonly use is Appian, which inherently integrates with MongoDB. This eliminates the need for selecting third-party databases or certifications, as it seamlessly works with MongoDB.

There is the need for a robust IDE for MongoDB. The existing PHP admin console doesn't meet the client's requirements effectively.    

I have been working with MariaDB for the past two years. 

It is stable. We have deployed several fraud implementations on Maria. While there have been occasional hiccups with replication and such, those can be addressed at the application level.

In terms of scalability, I don't perceive any issues with MongoDB, given the substantial volume of clients we serve.

I haven't encountered any blockers so far, which is why I haven't sought support.

Our technology partner, Appian, handles the provisioning, configurations, and instant spin-up of resources for us.

For clients predominantly using Microsoft technologies, especially Microsoft SQL, it aligns well with their technical stack. MS SQL is particularly suitable for reporting and analytics purposes.

It ultimately depends on the specific solution we are working on. However, overall, it is a good choice when considering factors like cost, performance, and other database practices. I don't foresee any significant challenges. I would rate it 7 out of 10.

I am currently using Visual Studio Code. I have used Visual Studio for about six months, along with GitHub. Additionally, I use GitLab for Azure orchestration.

The unit testing and Git are integrated. The searching is very extensive, which is helpful.

Visual Studio offers unit testing integration and extensive searching capabilities.

The Git extensions can be improved. The features available are very basic. Visual Studio should offer more extensive functionality in comparison to Git-focused software like GitTower or SmartGit.

I have been using Visual Studio Code for about six months.

I have not faced any issues in terms of stability.

We used to use Zoom for communication but have moved to Teams. GitLab provides what GitHub provides, so we don't use GitHub.

If you understand your project, you can install it without needing anyone else.

The IT department handles certain aspects, and I don't have information about it.

We are using Microsoft Teams instead of Zoom. I also mentioned GitLab, Redmine, Mongo, and GitHub Copilot is something we've considered but haven't started using.

I'm not the right person to ask specific questions as I do not have access to certain details.

We primarily use the solution for SaaS applications, where it is an integral part of our data management system.

The solution's features have effectively met our operational requirements as a standard SQL database.

There could be a command-line prompt for repairing the database and fixing indexes, similar to what was available in the old MyISAM storage engine.

I have been working with MariaDB for ten years.

I haven’t had any performance issues with MariaDB. Any problems we’ve encountered are typically related to the operating system or external factors like internet disruptions, not the database itself.

We have a small team of about three or four developers working with MariaDB. As for end users, the number varies depending on the application. Some of our SaaS applications support a few hundred users, while others might have thousands of users, depending on the client and project.

We transitioned to MariaDB after Oracle acquired MySQL. We continued using it just as we did with MySQL before the acquisition.

One issue I have experienced is with the InnoDB storage system. When a database crashes in InnoDB, it's essential to have a backup in a text file for restoration, but this is a common issue with MariaDB.

MariaDB differs from MySQL in several ways. Over the years, MariaDB has introduced many unique features that are not present in MySQL. It’s more open and community-driven, which allows for quicker adoption of new features and patches. Performance, especially in terms of scalability and handling large volumes of data, is a key difference. Additionally, MariaDB has better compatibility with some of the tools we use, making it a more attractive choice for our organization.

The setup was generally fine, but the configuration can be scattered across directories, which slightly complicates things. A more streamlined configuration process would be beneficial.

I set up the product's functionality replication on a virtual private network with a separate database server, which has significantly improved our data management. Although we have not yet scaled to the point of needing multiple clusters, the replication setup serves as a real-time backup for disaster recovery purposes. The product has been highly reliable, and regular updates as part of our server maintenance routine ensure smooth operation.

My overall experience with the product has been very positive. It has consistently delivered excellent performance and stability across our various projects. We have encountered very few issues over the years, and when we have, the community support has been strong, assisting us in resolving problems quickly. Its reliability is crucial for the critical applications we run.

The learning curve is quite manageable, especially for those already familiar with MySQL. The two products share many similarities, so transitioning from MySQL to this solution was relatively seamless for our team. Comprehensive documentation and active community support further simplify the learning process, making it easier for developers to get up to speed.

We have used it for a long time, proven very stable. Additionally, it is an excellent alternative to MySQL, especially considering the changes after Oracle's acquisition. The strong community support and integration with our existing infrastructure enhance its value.

I rate it a ten out of ten.