DBMS > Dgraph vs. IRONdb vs. JSqlDb vs. Microsoft Azure SQL Database vs. Snowflake

System Properties Comparison Dgraph vs. IRONdb vs. JSqlDb vs. Microsoft Azure SQL Database vs. Snowflake

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

JSqlDB seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Description

Distributed and scalable native Graph DBMS

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

JavaScript Query Language Database, stores JavaScript objects and primitives

Database as a Service offering with high compatibility to Microsoft SQL Server

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

Primary database model

Graph DBMS

Time Series DBMS

Document store
Object oriented DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	76.78
Rank	#16	Overall
	#11	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

dgraph.io

www.circonus.com/solutions/time-series-database/

jsqldb.org (offline)

azure.microsoft.com/en-us/products/azure-sql/database

www.snowflake.com

Technical documentation

dgraph.io/docs

docs.circonus.com/irondb/category/getting-started

docs.microsoft.com/en-us/azure/azure-sql

docs.snowflake.net/manuals/index.html

Developer

Dgraph Labs, Inc.

Circonus LLC.

Konrad von Backstrom

Microsoft

Snowflake Computing Inc.

Initial release

2016

2017

2018

2010

2014

Current release

V0.10.20, January 2018

0.8, December 2018

V12

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

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

C and C++

C++

Server operating systems

Linux
OS X
Windows

Linux

Linux
macOS
Windows

hosted

Data scheme

schema-free

yes

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

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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 (Circonus Analytics Query Language: CAQL)

yes

APIs and other access methods

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

HTTP API

ADO.NET
JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

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

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

JavaScript

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes, in Lua

functions in JavaScript

Transact SQL

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

yes

Automatic, metric affinity per node

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

configurable replication factor, datacenter aware

none

yes, with always 3 replicas available

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using RocksDB

yes

In-memory capabilities

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

User concepts

Access control

Planned for future releases

fine grained access rights according to SQL-standard

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.