DBMS > mSQL vs. OrigoDB vs. RDF4J vs. Snowflake vs. SurrealDB

System Properties Comparison mSQL vs. OrigoDB vs. RDF4J vs. Snowflake vs. SurrealDB

Editorial information provided by DB-Engines

Name

Description

mSQL (Mini SQL) is a simple and lightweight RDBMS

A fully ACID in-memory object graph database

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

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

A fully ACID transactional, developer-friendly, multi-model DBMS

Primary database model

Relational DBMS

Document store
Object oriented DBMS

RDF store

Relational DBMS

Document store
Graph DBMS

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

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.86
Rank	#203	Overall
	#34	Document stores
	#18	Graph DBMS

Website

hughestech.com.au/products/msql

Technical documentation

origodb.com/docs

rdf4j.org/documentation

docs.snowflake.net/manuals/index.html

surrealdb.com/docs

Developer

Hughes Technologies

Robert Friberg et al

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Snowflake Computing Inc.

SurrealDB Ltd

Initial release

1994

2009

under the name LiveDB

2004

2014

2022

Current release

4.4, October 2021

v1.5.0, May 2024

License

Commercial or Open Source

commercial

free licenses can be provided

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

Open Source

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

Rust

Server operating systems

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux
Windows

Linux
OS X
Unix
Windows

hosted

Linux
macOS
Windows

Data scheme

yes

RDF Schemas

yes

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

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

yes

Secondary indexes

yes

SQL

Support of SQL

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

SQL-like query language

APIs and other access methods

JDBC
ODBC

.NET Client API
HTTP API
LINQ

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

CLI Client
JDBC
ODBC

GraphQL
RESTful HTTP API
WebSocket

Supported programming languages

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net

Java
PHP
Python

JavaScript (Node.js)
Python

Deno
Go
JavaScript (Node.js)
Rust

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

Domain Events

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

client side managed; servers are not synchronized

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

depending on model

yes

Transaction concepts

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

ACID

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

in-memory storage is supported as well

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

Role based authorization

Users with fine-grained authorization concept, user roles and pluggable authentication

yes, based on authentication and database rules

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.