DBMS > Dgraph vs. Oracle NoSQL vs. SQLite vs. VelocityDB

System Properties Comparison Dgraph vs. Oracle NoSQL vs. SQLite vs. VelocityDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Widely used embeddable, in-process RDBMS

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Graph DBMS

Document store
Key-value store
Relational DBMS

Relational DBMS

Graph DBMS
Object oriented DBMS

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

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.05
Rank	#358	Overall
	#36	Graph DBMS
	#16	Object oriented DBMS

Website

dgraph.io

www.oracle.com/database/nosql/technologies/nosql

www.sqlite.org

velocitydb.com

Technical documentation

dgraph.io/docs

docs.oracle.com/en/database/other-databases/nosql-database/index.html

www.sqlite.org/docs.html

velocitydb.com/UserGuide

Developer

Dgraph Labs, Inc.

Oracle

Dwayne Richard Hipp

VelocityDB Inc

Initial release

2016

2011

2000

2011

Current release

23.3, December 2023

3.45.3 (15 April 2024), April 2024

7.x

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

Open Source

Public Domain

commercial

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

Server operating systems

Linux
OS X
Windows

Linux
Solaris SPARC/x86

server-less

Any that supports .NET

Data scheme

schema-free

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

optional

yes

not rigid because of 'dynamic typing' concept.

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

SQL-like DML and DDL statements

yes

SQL-92 is not fully supported

APIs and other access methods

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

RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

.Net

Supported programming languages

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

C
C#
Go
Java
JavaScript (Node.js)
Python

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

.Net

Server-side scripts

Stored procedures

Triggers

yes

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

configurable

ACID within a storage node (=shard)

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

off heap cache

yes

User concepts

Access control

Planned for future releases

Access rights for users and roles

Based on Windows Authentication

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.