DBMS > Google Cloud Datastore vs. Heroic vs. NebulaGraph vs. SAP Advantage Database Server vs. Snowflake

System Properties Comparison Google Cloud Datastore vs. Heroic vs. NebulaGraph vs. SAP Advantage Database Server vs. Snowflake

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

A distributed, linear scalable, high perfomant Graph DBMS

Low-cost RDBMS with access to ISAM and FoxPro data structures

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

Primary database model

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

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	2.23
Rank	#116	Overall
	#10	Graph DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

cloud.google.com/datastore

github.com/spotify/heroic

github.com/vesoft-inc/nebula
www.nebula-graph.io

www.sap.com/products/advantage-database-server.html

www.snowflake.com

Technical documentation

cloud.google.com/datastore/docs

spotify.github.io/heroic

docs.nebula-graph.io

docs.snowflake.net/manuals/index.html

Developer

Google

Spotify

Vesoft Inc.

Sybase, SAP

Snowflake Computing Inc.

Initial release

2008

2014

2019

1993

2014

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache Version 2.0 + Common Clause 1.0

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

Java

C++

Server operating systems

hosted

Linux

Linux
Windows

hosted

Data scheme

schema-free

Strong typed schema

yes

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

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

via Elasticsearch

yes

Nebula Graph internally uses the Key-Value store RocksDB for persistency. The vertices, edges, and their properties are stored as Key while their values are stored as Value. The primary indexes are per Key and secondary indexes are per Value.

yes

SQL

Support of SQL

SQL-like query language (GQL)

SQL-like query language

yes

APIs and other access methods

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

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Browser interface
console (shell)
Cypher Query Language
GO Object Graph Mapper
Java Object Graph Mapper
NGBatis

ORM framework for NebulaGraph and Spring-Boot
Proprietary native API
Python Object Graph Mapper
Query language nGQL

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

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

.Net
C++
Go
Java
PHP
Python

Delphi
Perl
PHP

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

using Google App Engine

user defined functions

yes

user defined functions

Triggers

Callbacks using the Google Apps Engine

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

yes

Causal Clustering using Raft protocol

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

yes

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 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.

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Relationships in graphs

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using RocksDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

caching of (temporary) tables can be configured

User concepts

Access control

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

Role-based access control

fine grained access rights according to SQL-standard

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

More information provided by the system vendor

Specific characteristics

NebulaGraph is a truly distributed, linearly scalable, lightning-fast graph database,...
» more

Competitive advantages

NebulaGraph boasts the world's only graph database solution that is able to host...
» more

Typical application scenarios

Social networking Fraud detection Knowledge graph Data warehouse management Anti...
» more

Key customers

Companies from a variety of industries have implemented NebulaGraph Database in production,...
» more

Market metrics

At our very early stage, NebulaGraph has already received over 10,000 stars on GitHub...
» more

Licensing and pricing models

NebulaGraph is open source and free to use under Apache 2.0 license.
» 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.