DBMS > RavenDB vs. Realm vs. Snowflake vs. SQL.JS vs. SWC-DB

System Properties Comparison RavenDB vs. Realm vs. Snowflake vs. SQL.JS vs. SWC-DB

Editorial information provided by DB-Engines

Name

Description

Open Source Operational and Transactional Enterprise NoSQL Document Database

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

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

Port of SQLite to JavaScript

A high performance, scalable Wide Column DBMS

Primary database model

Document store

Relational DBMS

Wide column store

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

Time Series DBMS

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

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	7.41
Rank	#52	Overall
	#8	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.63
Rank	#241	Overall
	#112	Relational DBMS

Score	0.08
Rank	#364	Overall
	#13	Wide column stores

Website

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

ravendb.net/docs

realm.io/docs

docs.snowflake.net/manuals/index.html

sql.js.org/documentation/index.html

Developer

Hibernating Rhinos

Realm, acquired by MongoDB in May 2019

Snowflake Computing Inc.

Alon Zakai

enhancements implemented by others

Alex Kashirin

Initial release

2010

2014

2012

2020

Current release

5.4, July 2022

0.5, April 2021

License

Commercial or Open Source

Open Source

AGPL version 3, commercial license available

Open Source

commercial

Open Source

GPL V3

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

JavaScript

C++

Server operating systems

Linux
macOS
Raspberry Pi
Windows

Android
Backend: server-less
iOS
Windows

hosted

server-less, requires a JavaScript environment (browser, Node.js)

Linux

Data scheme

schema-free

yes

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

yes

schema-free

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

SQL-like query language (RQL)

yes

SQL-92 is not fully supported

SQL-like query language

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

CLI Client
JDBC
ODBC

JavaScript API

Proprietary protocol
Thrift

Supported programming languages

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

.Net
Java

with Android only
Objective-C
React Native
Swift

JavaScript (Node.js)
Python

JavaScript

C++

Server-side scripts

Stored procedures

yes

runs within the applications so server-side scripts are unnecessary

user defined functions

Triggers

yes

Change Listeners

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

yes

none

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.

Immediate Consistency

none

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

except by serializing a db to a file

yes

In-memory capabilities

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

yes

In-Memory realm

yes

User concepts

Access control

Authorization levels configured per client per database

yes

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.