DBMS > MaxDB vs. RavenDB vs. Snowflake vs. Spark SQL vs. YTsaurus

System Properties Comparison MaxDB vs. RavenDB vs. Snowflake vs. Spark SQL vs. YTsaurus

Editorial information provided by DB-Engines

Name

Description

A robust and reliable RDBMS optimized to run all major SAP solutions

Open Source Operational and Transactional Enterprise NoSQL Document Database

Cloud-based data warehousing service for structured and semi-structured data

Spark SQL is a component on top of 'Spark Core' for structured data processing

YTsaurus is an open source platform for distributed storage and processing.

Primary database model

Relational DBMS

Document store

Relational DBMS

Document store
Key-value store

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	2.26
Rank	#114	Overall
	#55	Relational DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Score	0.21
Rank	#324	Overall
	#45	Document stores
	#48	Key-value stores

Website

Technical documentation

maxdb.sap.com/documentation

ravendb.net/docs

docs.snowflake.net/manuals/index.html

spark.apache.org/docs/latest/sql-programming-guide.html

ytsaurus.tech/docs/en

Developer

SAP, acquired from Software AG (Adabas-D) in 1997

Hibernating Rhinos

Snowflake Computing Inc.

Apache Software Foundation

Yandex

Initial release

1984

2010

2014

2023

Current release

7.9.10.12, February 2024

5.4, July 2022

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

commercial

Limited community edition free

Open Source

AGPL version 3, commercial license available

commercial

Open Source

Apache 2.0

Open Source

Apache License, Version 2.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Scala

C++

Server operating systems

AIX
HP-UX
Linux
Solaris
Windows

Linux
macOS
Raspberry Pi
Windows

hosted

Linux
OS X
Windows

Ubuntu

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Typing

predefined data types such as float or date

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (RQL)

yes

SQL-like DML and DDL statements

YQL, an SQL-based language, is supported

APIs and other access methods

ADO.NET
JDBC
ODBC
WebDAV

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

CLI Client
JDBC
ODBC

JDBC
ODBC

Supported programming languages

.Net
C#
Java
Perl
PHP
Python

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript (Node.js)
Python

Java
Python
R
Scala

C++
Go
Java
JavaScript
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

yes, utilizing Spark Core

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

yes

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

ACID, Cluster-wide transaction available

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

fine grained access rights according to SQL-standard

Authorization levels configured per client per database

Users with fine-grained authorization concept, user roles and pluggable authentication

Access Control Lists

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.