DBMS > RavenDB vs. Rockset vs. Snowflake vs. XTDB

System Properties Comparison RavenDB vs. Rockset vs. Snowflake vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Open Source Operational and Transactional Enterprise NoSQL Document Database

A scalable, reliable search and analytics service in the cloud, built on RocksDB

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

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Document store

Relational DBMS

Document store

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

Relational DBMS
Search engine

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

Score	3.01
Rank	#101	Overall
	#17	Document stores

Score	0.84
Rank	#209	Overall
	#35	Document stores

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Score	0.09
Rank	#351	Overall
	#47	Document stores

Website

ravendb.net

rockset.com

www.snowflake.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

ravendb.net/docs

docs.rockset.com

docs.snowflake.net/manuals/index.html

www.xtdb.com/docs

Developer

Hibernating Rhinos

Rockset

Snowflake Computing Inc.

Juxt Ltd.

Initial release

2010

2019

2014

2019

Current release

5.4, July 2022

1.19, September 2021

License

Commercial or Open Source

Open Source

AGPL version 3, commercial license available

commercial

Open Source

MIT License

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++

Clojure

Server operating systems

Linux
macOS
Raspberry Pi
Windows

hosted

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

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

schema-free

Typing

predefined data types such as float or date

dynamic typing

yes

yes, extensible-data-notation format

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.

ingestion from XML files supported

yes

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language (RQL)

Read-only SQL queries, including JOINs

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

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

HTTP REST

CLI Client
JDBC
ODBC

HTTP REST
JDBC

Supported programming languages

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

Go
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

Clojure
Java

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

Sharding

Automatic sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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.

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID, Cluster-wide transaction available

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

User concepts

Access control

Authorization levels configured per client per database

Access rights for users and organizations can be defined via Rockset console

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.