DBMS > Dgraph vs. Hive vs. Postgres-XL vs. Snowflake vs. Transbase

System Properties Comparison Dgraph vs. Hive vs. Postgres-XL vs. Snowflake vs. Transbase

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

data warehouse software for querying and managing large distributed datasets, built on Hadoop

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

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

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Graph DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	61.17
Rank	#18	Overall
	#12	Relational DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

www.transaction.de/en/products/transbase.html

Technical documentation

dgraph.io/docs

cwiki.apache.org/confluence/display/Hive/Home

www.postgres-xl.org/documentation

docs.snowflake.net/manuals/index.html

www.transaction.de/en/products/transbase/features.html

Developer

Dgraph Labs, Inc.

Apache Software Foundation

initially developed by Facebook

Snowflake Computing Inc.

Transaction Software GmbH

Initial release

2016

2012

2014

since 2012, originally named StormDB

2014

1987

Current release

3.1.3, April 2022

10 R1, October 2018

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2

Open Source

Mozilla public license

commercial

free development license

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

C and C++

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

Linux
macOS

hosted

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

yes

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

yes

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

XML type, but no XML query functionality

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

distributed, parallel query execution

yes

APIs and other access methods

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

JDBC
ODBC
Thrift

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

C++
Java
PHP
Python

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

JavaScript (Node.js)
Python

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

horizontal partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

selectable replication factor

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

MVCC

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

Access rights for users, groups and roles

fine grained access rights according to SQL-standard

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

fine grained access rights according to SQL-standard

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.