DBMS > Dgraph vs. Google Cloud Datastore vs. Oracle vs. Sadas Engine vs. WakandaDB

System Properties Comparison Dgraph vs. Google Cloud Datastore vs. Oracle vs. Sadas Engine vs. WakandaDB

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

Widely used RDBMS

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

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

dgraph.io

cloud.google.com/datastore

www.oracle.com/database

www.sadasengine.com

wakanda.github.io

Technical documentation

dgraph.io/docs

cloud.google.com/datastore/docs

docs.oracle.com/en/database

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

wakanda.github.io/doc

Developer

Dgraph Labs, Inc.

Google

Oracle

SADAS s.r.l.

Wakanda SAS

Initial release

2016

2008

1980

2006

2012

Current release

23c, September 2023

8.0

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

restricted free version is available

commercial

free trial version available

Open Source

AGPLv3, extended commercial license available

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 and C++

C++

C++, JavaScript

Server operating systems

Linux
OS X
Windows

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

AIX
Linux
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

yes

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (GQL)

yes

with proprietary extensions

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
ODP.NET
Oracle Call Interface (OCI)

JDBC
ODBC
Proprietary protocol

RESTful HTTP API

Supported programming languages

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

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

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

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

JavaScript

Server-side scripts

Stored procedures

using Google App Engine

PL/SQL

also stored procedures in Java possible

yes

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

Sharding, horizontal partitioning

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Multi-source replication using Paxos

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

can be realized in PL/SQL

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

ACID

isolation level can be parameterized

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

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

managed by 'Learn by Usage'

User concepts

Access control

Planned for future releases

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

fine grained access rights according to SQL-standard

Access rights for users, groups and roles according to SQL-standard

yes

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.