DBMS > MonetDB vs. RavenDB vs. Snowflake vs. Trafodion

System Properties Comparison MonetDB vs. RavenDB vs. Snowflake vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

A relational database management system that stores data in columns

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

Transactional SQL-on-Hadoop DBMS

Primary database model

Relational DBMS

Document store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	1.72
Rank	#145	Overall
	#67	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

Technical documentation

www.monetdb.org/Documentation

ravendb.net/docs

docs.snowflake.net/manuals/index.html

trafodion.apache.org/documentation.html

Developer

MonetDB BV

Hibernating Rhinos

Snowflake Computing Inc.

Apache Software Foundation, originally developed by HP

Initial release

2004

2010

2014

Current release

Dec2023 (11.49), December 2023

5.4, July 2022

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Mozilla Public License 2.0

Open Source

AGPL version 3, commercial license available

commercial

Open Source

Apache 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++, Java

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS
Raspberry Pi
Windows

hosted

Linux

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 2003 with some extensions

SQL-like query language (RQL)

yes

APIs and other access methods

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

.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

ADO.NET
JDBC
ODBC

Supported programming languages

C
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

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

JavaScript (Node.js)
Python

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes, in SQL, C, R

yes

user defined functions

Java Stored Procedures

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding via remote tables

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication available in experimental status

Multi-source replication

yes

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

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

fine grained access rights according to SQL-standard

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.