DBMS > Dgraph vs. Google Cloud Datastore vs. GridDB vs. Kinetica vs. Snowflake

System Properties Comparison Dgraph vs. Google Cloud Datastore vs. GridDB vs. Kinetica vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

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

Scalable in-memory time series database optimized for IoT and Big Data

Fully vectorized database across both GPUs and CPUs

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

Primary database model

Secondary database models

Key-value store
Relational DBMS

Spatial DBMS
Time Series DBMS

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

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	2.09
Rank	#120	Overall
	#10	Time Series DBMS

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

dgraph.io

cloud.google.com/datastore

griddb.net

www.kinetica.com

www.snowflake.com

Technical documentation

dgraph.io/docs

cloud.google.com/datastore/docs

docs.griddb.net

docs.kinetica.com

docs.snowflake.net/manuals/index.html

Developer

Dgraph Labs, Inc.

Google

Toshiba Corporation

Kinetica

Snowflake Computing Inc.

Initial release

2016

2008

2013

2012

2014

Current release

5.1, August 2022

7.1, August 2021

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also 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

C++

C, C++

Server operating systems

Linux
OS X
Windows

hosted

Linux

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

yes, details here

yes

numerical, string, blob, geometry, boolean, timestamp

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 (GQL)

SQL92, SQL-like TQL (Toshiba Query Language)

SQL-like DML and DDL statements

yes

APIs and other access methods

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

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

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

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

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

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

C++
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

using Google App Engine

user defined functions

Triggers

Callbacks using the Google Apps Engine

yes

triggers when inserted values for one or more columns fall within a specified range

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Multi-source replication using Paxos

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

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 within container, eventual consistency across containers

Immediate Consistency or Eventual Consistency depending on configuration

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

ACID at container level

ACID

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

GPU vRAM or System RAM

User concepts

Access control

Planned for future releases

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

Access rights for users can be defined per database

Access rights for users and roles on table level

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

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

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.