MariaDB is an open-source relational database made by the original developers of MySQL, supported by the MariaDB Foundation and a community of developers. The community states recent additional capabilities as including clustering with Galera Cluster 4, compatibility with Oracle Database, and Temporal Data Tables, allowing one to query the data as it stood at any point in the past.
N/A
SingleStore
Score 7.5 out of 10
N/A
SingleStore aims to enable organizations to scale from one to one million customers, handling SQL, JSON, full text and vector workloads in one unified platform.
MariaDB is perhaps the best open source database server available, combining a wide range of supported platforms, MySQL compatibility, a low footprint, and reasonably high performance. If you have cost constraints, or limited server resources, I recommend MariaDB, particularly …
MS SQL Server is like a BlackBox in many cases. Honestly we did not need advanced functionality that SQL server offers, just a plain DBMS. MariaDB is easier to manage, cross operating system, "lighter" with better performances than SQL server. We went with MariaDB Platform even …
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 …
We tried Percona also, but we sometimes having trouble with it and on some cases it having lesser performance than MariaDB. MySQL is the the facto standard, we use this only in scenario that it cannot be replaced by MariaDB. MSSQL is used only if the client ask for Windows …
We were already wanting to migrate away from Cassandra for reasons of stability, cost (more servers were needed), and our data storage model. We evaluated PostgreSQL but passed on it due to being more familiar with MariaDB. Also we needed something that could do multi-region …
MariaDB is very similar to MySQL, but MariaDB has more alternative database engines and ideas for the future where MySQL is offers the stable and more mature version (if not stale).
(With and without RAC) My company migrated from Oracle to MariaDB. While MariaDB has some limitations (if you are used to Oracle) it has been much easier and cheaper (in several ways) to operate and has more than met my company's needs.
MariaDB is the clear winner compared to any other database I've used. Reliable, scale-able, affordable--you name the consideration and MariaDB is the winner.
MariaDB is much easier to set up and maintain compared to PostgreSQL makes it much faster to launch our application and relatively easier to upgrade its version so we can make sure the installed version is up to date with the latest patch, which is especially important if we …
MySQL is still a great solution, but MariaDB offers a more extensive set of free features than are available for MySQL. We also feel more confident that MariaDB will remain free to use over time. End users haven't noticed much of a difference, but from a development cost …
MariaDB stacks up the the competition just fine. Due to is ture open source nature we do not have to worry about licencing and spending money on nothing. Moreover, MariaDB does everything that we need to get done. We can run data that is a million rows or many smaller projects …
MariaDB provided the best fit for our business in upgrading legacy systems which were originally designed to use MySQL as a backend. By using MariaDB, no changes to the overall systems needed to be altered, reducing the time needed to upgrade everything. Other solutions …
Thanks to MySQL compatibility, everything you've learned while using it can be utilized when using MariaDB. Therefore it's a better choice than MongoDB and MSSQL if you're looking to switch away from MySQL. MariaDB is also a very mature and stable product, unlike MongoDB that …
MariaDB is cheaper than Oracle Database and MSSQL server. MySQL owned by Oracle. So MariaDB has too many forks, but enough people in the community. PostgreSQL has a larger community and better administration. However, it s not like MariaDB w/ Galera. MariaDB is not good for …
We know others DB alternatives like MySQL, Microsoft SQLServer, PostgreSQL. We selected MariaDB because it offer advanced features like active-active cluster, with no costs and easy to learn. With MariaDB was easy to migrate ours applications that use MySQL, with no …
We selected MariaDB over MySQL because of their true open source model and performance optimizations. It was also helpful that it is a drop-in replacement for MySQL so there was no need to update our various software drivers.
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.
I can only compare it with Exasol, which I have used a similar base, which manages the Hadoop scheme and is very similar to SingleStore. SingleStore has many advantages: being in the cloud, with just a couple of clicks I can increase the capacity, the configuration is super …
first of all SingleStoreis a cluster with high availability and easy to use. you need to design you tables / procedures such in a way that your SingleStore perform well and with handle heavy load
Reduces database sprawl, ETL costs, infrastructure expenses, etc. Supports horizontal scaling, unlike PostgreSQL & Aurora, and real-time analytics and fast transactions (HTAP), unlike Snowflake & ClickHouse.Handles high-volume workloads with thousands of concurrent queries. No …
SingleStore (memsql) out performs based on our analysis with sample data sets within org. We could see limitations with other products which SingleStore can overcall like scaling with data while performing with similar SLA. It also has the advantage of row store and column …
SingleStore outperforms Snowflake in real-time analytics and transactional workloads but lags in large-scale batch processing. Compared to MongoDB Atlas, SingleStore excels in complex SQL queries and joins, while MongoDB handles unstructured, document-based data better. Its …
Greenplum is good in handling very large amount of data. Concurrency in Greenplum was a major problem. Features available in SingleStore like Pipelines and in memory features are not available in Greenplum.
Gemfire was not scaling well like SingleStore. Support of both …
We previously used Bigquery for our application, and a single store gave us very good performance over Bigquery. But the comparison is not apples to apples, as Bigquery is more of a data warehousing solution.
SingleStore is just a bigger engine with more capability. Its ability to handle larger data sets with ease is its biggest advantage. These other database solutions are great for smaller scale projects that don't include large data sets but Singlestore greatly out performs in …
It has more APIs and other access methods. It has a multi-version concurrency control (MVCC) Distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in …
Its easier to query and faster. Ingestion is for the most part easier to understand and monitor and directly integrated with other storage solution products we use such as AWS S3. Singlestore overall is a better database to serve up an application large amounts of data very …
SingleStore is built for fast data ingestion and fast queries against large tables (> billions of rows). This is possible because of the column store engine that SingleStore uses. SingleStore also support a memory engine. Pipelines is also another big advantage. Being able to …
We knew early on that MySQL (Amazon Aurora) would not be suitable for this workload as it cannot query our time series data as fast as SingleStore. We also use MongoDB Atlas for another application but we could not achieve the raw speed we saw from SingleStore. Our technical …
We were initially using AWS Aurora which worked well at the time but as we grew it just felt like a lumbering beast - even with tier upgrades. We started looking at caching & search options to help make searches faster - we were already using redis. We looked at and even …
Timescale was the biggest alternative option we looked at for SingleStore, however the requirement to learn a new syntax (due to not being SQL compatible) was our biggest pain point.
Supporting a new language would require alterations to the Laravel framework, as this only …
SingleStore provides an abstraction layer in managing a sharded database solution reducing complexity for the FLOWD team. Coupled with the SingleStore Managed Service, we are partnering with SingleStore to provide FLOWD services to various utilities & councils.
SingleStore is eons faster than other database providers, and it absolutely crushes calculations & aggregations. While other providers may have a few quality of life enhancements over SingleStore, the speed benefits of SS far outweigh the cons. At the end of the day, speed …
SingleStore provides performance for real-time data analytics application where as Snowflake is more for data engineers and not fast enough for real-time data analytics apps.
As I said before, we felt that running queries on BigQuery for every query is really slow, especially from an user point of view. After seeing the drastically improved latency of SingleStore we decided to use to solve this issue. We currently use it to run low volume queries …
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.
Well-Suited Scenarios: Real-Time Analytics: Financial trading platforms requiring instant insights. Operational Dashboards: Retail businesses monitoring live sales. IoT Data Processing: Smart device monitoring with high data ingestion. Fraud Detection: Banks detect suspicious transactions instantly. Less Appropriate Scenarios: Archival Storage: Cold data storage with infrequent access. Low-Volume Workloads: Small-scale apps with minimal data processing needs. Complex ETL Pipelines: Heavy data transformations without real-time demands.
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.
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.
It does not release a patch to have back porting; it just releases a new version and stops support; it's difficult to keep up to that pace.
Support engineers lack expertise, but they seem to be improving organically.
Lacks enterprise CDC capability: Change data capture (CDC) is a process that tracks and records changes made to data in a database and then delivers those changes to other systems in real time.
For enterprise-level backup & restore capability, we had to implement our model via Velero snapshot backup.
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.
[Until it is] supported on AWS ECS containers, I will reserve a higher rating for SingleStore. Right now it works well on EC2 and serves our current purpose, [but] would look forward to seeing SingleStore respond to our urge of feature in a shorter time period with high quality and security.
When it comes to ingestion speed, SingleStore is probably at the top. Being able to create pipelines using SQL to ingest data from S3, Kafka, and other sources, is a great advantages. This means you can dynamically ingest data by customizing your SQL queries. SingleStore pipelines are pretty sophisticated, yet very simple. Few lines of codes and you are ingesting data, while still able to perform analytical queries on your billions of row tables.
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.
The support deep dives into our most complexed queries and bizarre issues that sometimes only we get comparing to other clients. Our special workload (thousands of Kafka pipelines + high concurrency of queries). The response match to the priority of the request, P1 gets immediate return call. Missing features are treated, they become a client request and being added to the roadmap after internal consideration on all client needs and priority. Bugs are patched quite fast, depends on the impact and feasible temporary workarounds. There is no issue that we haven't got a proper answer, resolution or reasoning
We allowed 2-3 months for a thorough evaluation. We saw pretty quickly that we were likely to pick SingleStore, so we ported some of our stored procedures to SingleStore in order to take a deeper look. Two SingleStore people worked closely with us to ensure that we did not have any blocking problems. It all went remarkably smoothly.
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.
Reduces database sprawl, ETL costs, infrastructure expenses, etc. Supports horizontal scaling, unlike PostgreSQL & Aurora, and real-time analytics and fast transactions (HTAP), unlike Snowflake & ClickHouse.Handles high-volume workloads with thousands of concurrent queries. No need for ETL processes, unlike BigQuery & Snowflake. Works with JSON, relational, and key-value data, unlike ClickHouse.
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.
Lower operational complexity - Installation and maintenance is pretty easy
Object scale when used can compete with Traditional Warehouse Systems like Teradata, Netezza, Greenplum
Adds lot of value to the business like couple of operations which never worked in traditional DBMS including HANA, Oracle In Memory, SQL Server In Memory just flew in SingleStore