DBMS > RavenDB vs. Sequoiadb vs. Snowflake vs. Transbase

System Properties Comparison RavenDB vs. Sequoiadb vs. Snowflake vs. Transbase

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

NewSQL database with distributed OLTP and SQL

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

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Document store

Document store
Relational DBMS

Relational DBMS

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	0.45
Rank	#261	Overall
	#41	Document stores
	#122	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

ravendb.net

www.sequoiadb.com

www.snowflake.com

www.transaction.de/en/products/transbase.html

Technical documentation

ravendb.net/docs

www.sequoiadb.com/en/index.php?m=Files&a=index

docs.snowflake.net/manuals/index.html

www.transaction.de/en/products/transbase/features.html

Developer

Hibernating Rhinos

Sequoiadb Ltd.

Snowflake Computing Inc.

Transaction Software GmbH

Initial release

2010

2013

2014

1987

Current release

5.4, July 2022

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

AGPL version 3, commercial license available

Open Source

Server: AGPL; Client: Apache V2

commercial

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

C and C++

Server operating systems

Linux
macOS
Raspberry Pi
Windows

Linux

hosted

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

yes

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

yes

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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

SQL-like query language (RQL)

SQL-like query language

yes

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

proprietary protocol using JSON

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

.Net
C++
Java
PHP
Python

JavaScript (Node.js)
Python

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

JavaScript

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

yes

Source-replica replication

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

Document is locked during a transaction

ACID

yes

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

Authorization levels configured per client per database

simple password-based access control

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.