DBMS > Apache Drill vs. mSQL vs. OrigoDB vs. RDF4J vs. Snowflake

System Properties Comparison Apache Drill vs. mSQL vs. OrigoDB vs. RDF4J vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

Primary database model

Document store
Relational DBMS

Relational DBMS

Document store
Object oriented DBMS

RDF store

Relational DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

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

Website

drill.apache.org

hughestech.com.au/products/msql

origodb.com

rdf4j.org

www.snowflake.com

Technical documentation

drill.apache.org/docs

origodb.com/docs

rdf4j.org/documentation

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Hughes Technologies

Robert Friberg et al

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

Snowflake Computing Inc.

Initial release

2012

1994

2009

under the name LiveDB

2004

2014

Current release

1.20.3, January 2023

4.4, October 2021

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

free licenses can be provided

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

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

Server operating systems

Linux
OS X
Windows

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

Linux
Windows

Linux
OS X
Unix
Windows

hosted

Data scheme

schema-free

yes

RDF Schemas

yes

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

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

SQL SELECT statement is SQL:2003 compliant

A subset of ANSI SQL is implemented

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

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

Supported programming languages

C++

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net

Java
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

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

Sharding

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

yes

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

Depending on the underlying data source

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.

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

Role based authorization

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.