Apache Cassandra vs. MariaDB Platform

Cassandra excels in a broad range of applications -- especially if you understand its data model and write your applications accordingly. It's an excellent choice for time-series data, and a poor choice for application queues. It performs the best if you can simply record history and compute from it, rather than going back and editing or deleting things a lot.

Incentivized

Our installation scenario is a MariaDB cluster composed of 3 nodes to achieve high availability in the service and in this way the application that accesses the backend (MariaDB) is always working and is not down at any time.

To achieve high performance of the application when accessing the database, a MariaDB MaxScale has been mounted that acts as a proxy for queries to the database.

Incentivized

• High Availability - we utilize the data replication features of Cassandra. This enables us to access our data even when several nodes have gone down
• Data Locality - our architecture combines Cassandra storage nodes and computation nodes in the same machine. This enables us to utilize data locality and limit expensive network IO to read data.
• Elasticity - Cassandra is a shared nothing architecture. Nodes can be added very easily and they discover the network topology. As soon as a node has joined the Cassandra ring, the data is redistributed among the existing nodes and streamed to it automatically.

Incentivized

• MariaDB does well with PHP or Python (django) in a web environment. Developers are able to work quickly.
• MariaDB is extremely well documented and has a gigantic support community. If you need ask a question on how to do things you can go to many placces online and find answers quickly.
• MariaDB is fast! Queries with tens of thousands of rows are quick.
• MariaDB is highly compatible with Oracle's MySQL. Basically the same thing but more open and with a brighter future.
• With MariaDB it is so easy to import and export data, and backups are a cinch. This saves me so much time as compared to other RDBMS.

Incentivized

• No Ad-Hoc Queries: Cassandra data storage layer is basically a key-value storage system. This means that you must "model" your data around the queries you want to surface, rather than around the structure of the data itself.
• There are no aggregations queries available in Cassandra.
• Not fit for transactional data.

Incentivized

• Driver Support - Some third party applications use database drivers that cause unexplained slowness with MariaDB. This can be worked around by using the MySQL drivers, but it's not clear what causes the problem in the first place.
• Support - While online communities are helpful in diagnosing problems, there isn't as much professional documentation/support available for MariaDB as some of the other major database options.
• Data Visualization - It would be helpful if there were more built in options for analyzing statistics and generating reports.

Incentivized

I would recommend Cassandra DB to those who know their use case very well, as well as know how they are going to store and retrieve data. If you need a guarantee in data storage and retrieval, and a DB that can be linearly grown by adding nodes across availability zones and regions, then this is the database you should choose.

Incentivized

It’s great tool but it can be complicated when it comes administration and maintenance.

Incentivized

MariaDB is very usable and stable to be used in production settings as an alternative to MySQL. The shortcomings of SQL are present but well understood in the community, and if the decision were to be made again, I would choose MariaDB over MySQL on future projects.

Incentivized

Sometimes instead giving straight answer, we ‘re getting transfered to talk professional service.

Incentivized

Yes, I would recommend MariaDB Platform support because they answer very fast and with detailed information. They also help you with the design of the storage infrastructure, not only with the maintenance problems. On the other hand, this service is a bit expensive.

Incentivized

Apache Cassandra has the best of both worlds, it is a Java based NoSQL, linearly scalable, best in class
tunable performance across different workloads, fault tolerant, distributed, masterless, time series database. We have used both Apache HBase and MongoDB for some use cases which were within hadoop setup and JSON (JavaScript Object Notation) document store respectively, but given the overall factors favoring Apache Cassandra, it is a technology choice for multiple platforms!

Incentivized

It did not always compete against these technologies. Most of the time, it was complementing these databases for certain use cases to help provide a much more complete database. This makes more users want to use it to explore new solutions that help users. This is our target and how [we] work with MariaDb.

Incentivized

• The open source version of Cassandra is only suggested for learning the basic concepts and play with its core features. Unless you really want to invest a lot in your developers and architects knowing every detail of Cassandra, I prefer the DataStax enterprise version. Although the license cost is relatively high, I think they it is worth it. I'm thinking about the support, the monitoring tool OpsCenter, and the integration of Solr and Spark (for data analysis).
• Cassandra didn't fully replace our old and traditional relation database Oracle. In addition, it opens another door for us to deal with some special business use cases that NoSQL database can do better in a more feasible and efficient way.

Incentivized

• MariaDB has saved us enormously on licensing compared to our previous DB software vendor.
• In service, it has enabled us (speaking as the internal DB team here) to provide better service to the other teams in the company as well as our customers, with less staff.
• The level of hardware required for adequate performance, in our environment, has been much lower. Those savings have been substantial, above and beyond savings on licensing and DBA staffing levels.

Incentivized