DBMS > Dgraph vs. EsgynDB vs. Google Cloud Datastore vs. Sadas Engine vs. Tkrzw

System Properties Comparison Dgraph vs. EsgynDB vs. Google Cloud Datastore vs. Sadas Engine vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

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	4.49
Rank	#79	Overall
	#12	Document stores

Score	0.03
Rank	#379	Overall
	#156	Relational DBMS

Score	0.09
Rank	#354	Overall
	#51	Key-value stores

Website

dgraph.io

www.esgyn.cn

cloud.google.com/datastore

www.sadasengine.com

dbmx.net/tkrzw

Technical documentation

dgraph.io/docs

cloud.google.com/datastore/docs

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Dgraph Labs, Inc.

Esgyn

Google

SADAS s.r.l.

Mikio Hirabayashi

Initial release

2016

2015

2008

2006

2020

Current release

8.0

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

free trial version available

Open Source

Apache Version 2.0

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++, Java

C++

Server operating systems

Linux
OS X
Windows

Linux

hosted

AIX
Linux
Windows

Linux
macOS

Data scheme

schema-free

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (GQL)

yes

APIs and other access methods

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

ADO.NET
JDBC
ODBC

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JDBC
ODBC
Proprietary protocol

Supported programming languages

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

All languages supporting JDBC/ODBC/ADO.Net

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

.Net
C
C#
C++
Groovy
Java
PHP
Python

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

using Google App Engine

Triggers

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Multi-source replication between multi datacenters

Multi-source replication using Paxos

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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.

yes

managed by 'Learn by Usage'

yes

using specific database classes

User concepts

Access control

Planned for future releases

fine grained access rights according to SQL-standard

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access rights for users, groups and roles 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

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 Raises $6M in Seed Funding
20 July 2022, FinSMEs

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

provided by Google News

Google Cloud Stops Exit Fees
12 January 2024, Spiceworks News and Insights

BigID Data Intelligence Platform Now Available on Google Cloud Marketplace
6 November 2023, PR Newswire

Best cloud storage of 2024
3 April 2024, TechRadar

What Is Google Cloud Platform?
28 August 2023, Simplilearn

Compare Google Cloud Storage vs. Google Drive for enterprises
9 November 2023, TechTarget

provided by Google News

Share this page