DBMS > Dgraph vs. Graph Engine vs. HEAVY.AI vs. jBASE vs. Snowflake

System Properties Comparison Dgraph vs. Graph Engine vs. HEAVY.AI vs. jBASE vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

A robust multi-value DBMS comprising development tools and middleware

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

Primary database model

Graph DBMS

Graph DBMS
Key-value store

Relational DBMS

Multivalue DBMS

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	1.41
Rank	#159	Overall
	#3	Multivalue DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

dgraph.io

www.graphengine.io

github.com/heavyai/heavydb
www.heavy.ai

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

www.snowflake.com

Technical documentation

dgraph.io/docs

www.graphengine.io/docs/manual

docs.heavy.ai

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

docs.snowflake.net/manuals/index.html

Developer

Dgraph Labs, Inc.

Microsoft

HEAVY.AI, Inc.

Rocket Software (formerly Zumasys)

Snowflake Computing Inc.

Initial release

2016

2010

2016

1991

2014

Current release

5.10, January 2022

5.7

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

MIT License

Open Source

Apache Version 2; enterprise edition available

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

.NET and C

C++ and CUDA

Server operating systems

Linux
OS X
Windows

.NET

Linux

AIX
Linux
Windows

hosted

Data scheme

schema-free

yes

schema-free

yes

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

Typing

predefined data types such as float or date

yes

optional

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

yes

Embedded SQL for jBASE in BASIC

yes

APIs and other access methods

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

RESTful HTTP API

JDBC
ODBC
Thrift
Vega

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

CLI Client
JDBC
ODBC

Supported programming languages

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

C#
C++
F#
Visual Basic

All languages supporting JDBC/ODBC/Thrift
Python

.Net
Basic
Jabbascript
Java

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

yes

horizontal partitioning

Sharding

Round robin

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

Planned for future releases

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

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.