DBMS > Dgraph vs. Drizzle vs. EsgynDB vs. H2GIS vs. TimescaleDB

System Properties Comparison Dgraph vs. Drizzle vs. EsgynDB vs. H2GIS vs. TimescaleDB

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

Distributed and scalable native Graph DBMS

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Spatial extension of H2

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Secondary database models

Relational DBMS

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

Score	1.48
Rank	#158	Overall
	#15	Graph DBMS

Score	0.23
Rank	#319	Overall
	#141	Relational DBMS

Score	0.05
Rank	#372	Overall
	#7	Spatial DBMS

Score	4.87
Rank	#74	Overall
	#4	Time Series DBMS

Website

Technical documentation

dgraph.io/docs

www.h2gis.org/docs/home

docs.timescale.com

Developer

Dgraph Labs, Inc.

Drizzle project, originally started by Brian Aker

Esgyn

CNRS

Timescale

Initial release

2016

2008

2015

2013

2017

Current release

7.2.4, September 2012

2.13.0, November 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GNU GPL

commercial

Open Source

LGPL 3.0

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

C++, Java

Java

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
OS X

Linux

Linux
OS X
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

with proprietary extensions

yes

full PostgreSQL SQL syntax

APIs and other access methods

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

JDBC

ADO.NET
JDBC
ODBC

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

Supported programming languages

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

C
C++
Java
PHP

All languages supporting JDBC/ODBC/ADO.Net

Java

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

Java Stored Procedures

yes

based on H2

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

none

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Multi-source replication
Source-replica replication

Multi-source replication between multi datacenters

yes

based on H2

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

yes, multi-version concurrency control (MVCC)

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.

yes

User concepts

Access control

Planned for future releases

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

yes

based on H2

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

Dgraph on AWS: Setting up a horizontally scalable graph database | Amazon Web Services
1 September 2020, AWS Blog

Dgraph launches Slash GraphQL, a GraphQL-native database Backend-as-a-Service
10 September 2020, TechCrunch

Dgraph Rises to the Top Graph Database on GitHub With 11 G2 Badges and 11M Downloads
26 May 2021, Business Wire

Dgraph GraphQL database users detail graph use cases
20 April 2021, TechTarget

provided by Google News

TimescaleDB Is a Vector Database Now, Too
25 September 2023, Datanami

Timescale Acquires PopSQL to Bring a Modern, Collaborative SQL GUI to PostgreSQL Developers
4 April 2024, PR Newswire

TimescaleDB for Azure Database for PostgreSQL to power IoT and time-series workloads | Azure updates
18 March 2019, Microsoft

Visualizing IoT Data at Scale With Hopara and TimescaleDB
16 May 2023, Embedded Computing Design

Timescale Valuation Rockets to Over $1B with $110M Round, Marking the Explosive Rise of Time-Series Data
22 February 2022, Business Wire

provided by Google News

Share this page