MariaDB implemetation first phase
August 05, 2016

MariaDB implemetation first phase

Anonymous | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User

Overall Satisfaction with MariaDB

The Engineering department uses MariaDB for its OLTP system. It solves the problem we had with NoSQL databases to give us an ACID compliant reliable database storage engine.
  • Gives us the flexibility to design data structures which can be joined to give data served by our APIs.
  • Provides us options to use multiple storage engines based on the data being stored.
  • Replication technology can definitely improve. Currently we face lot of issues with replication causing table locks.
  • Provide better troubleshooting tools out of the box, for example a comprehensive GUI like SSMS for SQL Server.
  • Alter table and add indexing is an overhead on large tables which causes replication and storage issues.
  • Positive - We have seen less time spent by support teams in investigations as they could join multiple tables to find the data.
  • Negative - We have seen a lot of table locks in the system due to replication and schema changes on large tables.
MariaDB costs much less than SQL Server to acquire and maintain. In comparison to Cassandra, it gives us operational use and helps in Agile development.
  • Well suited for medium scale read and write systems
  • Not suited for systems where write workloads are high and require multiple masters to support the volume