DBMS > Amazon SimpleDB vs. Google Cloud Datastore vs. NebulaGraph vs. SAP HANA vs. STSdb

System Properties Comparison Amazon SimpleDB vs. Google Cloud Datastore vs. NebulaGraph vs. SAP HANA vs. STSdb

Editorial information provided by DB-Engines

Name

Description

Hosted simple database service by Amazon, with the data stored in the Amazon Cloud.

There is an unrelated product called SimpleDB developed by Edward Sciore

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

A distributed, linear scalable, high perfomant Graph DBMS

In-memory, column based data store. Available as appliance or cloud service

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	1.88
Rank	#133	Overall
	#23	Key-value stores

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	2.23
Rank	#116	Overall
	#10	Graph DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.10
Rank	#357	Overall
	#51	Key-value stores

Website

aws.amazon.com/simpledb

cloud.google.com/datastore

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

www.sap.com/products/hana.html

github.com/STSSoft/STSdb4

Technical documentation

docs.aws.amazon.com/simpledb

cloud.google.com/datastore/docs

docs.nebula-graph.io

help.sap.com/hana

Developer

Amazon

Google

Vesoft Inc.

SAP

STS Soft SC

Initial release

2007

2008

2019

2010

2011

Current release

2.0 SPS07 (April 4, 2023), April 2023

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0 + Common Clause 1.0

commercial

Open Source

GPLv2, commercial license available

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

Server operating systems

hosted

Linux

Appliance or cloud-service

Windows

Data scheme

schema-free

Strong typed schema

yes

Typing

predefined data types such as float or date

yes, details here

yes

primitive types and user defined types (classes)

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

All columns are indexed automatically

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

RESTful HTTP API

gRPC (using protocol buffers) API
RESTful HTTP/JSON 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

JDBC
ODBC

.NET Client API

Supported programming languages

.Net
C
C++
Erlang
Java
PHP
Python
Ruby
Scala

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

.Net
C++
Go
Java
PHP
Python

C#
Java

Server-side scripts

Stored procedures

using Google App Engine

user defined functions

SQLScript, R

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding must be implemented in the application

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

Causal Clustering using Raft protocol

yes

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

Eventual Consistency
Immediate Consistency

can be specified for read operations

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

Relationships in graphs

yes

Transaction concepts

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

Concurrent data updates can be detected by the application

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

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

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

Role-based access control

yes

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.