DBMS > BaseX vs. EXASOL vs. MaxDB vs. RavenDB vs. Snowflake

System Properties Comparison BaseX vs. EXASOL vs. MaxDB vs. RavenDB vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	1.73
Rank	#142	Overall
	#4	Native XML DBMS

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	2.32
Rank	#112	Overall
	#55	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

Technical documentation

docs.basex.org

www.exasol.com/resources

maxdb.sap.com/documentation

ravendb.net/docs

docs.snowflake.net/manuals/index.html

Developer

BaseX GmbH

Exasol

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

Hibernating Rhinos

Snowflake Computing Inc.

Initial release

2007

2000

1984

2010

2014

Current release

10.7, August 2023

7.9.10.12, February 2024

5.4, July 2022

License

Commercial or Open Source

Open Source

BSD license

commercial

Limited community edition free

Open Source

AGPL version 3, commercial license available

commercial

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

Java

C++

Server operating systems

Linux
OS X
Windows

AIX
HP-UX
Linux
Solaris
Windows

Linux
macOS
Raspberry Pi
Windows

hosted

Data scheme

schema-free

yes

schema-free

yes

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

Typing

predefined data types such as float or date

XQuery supports types

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

APIs and other access methods

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

.Net
JDBC
ODBC
WebSocket

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

Supported programming languages

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

Java
Lua
Python
R

.Net
C#
Java
Perl
PHP
Python

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

yes

user defined functions

Triggers

yes

via events

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

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

multiple readers, single writer

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.

yes

User concepts

Access control

Users with fine-grained authorization concept on 4 levels

Access rights for users, groups and roles according to SQL-standard

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

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.