DBMS > Dgraph vs. Infobright vs. Microsoft Azure SQL Database vs. Oracle Coherence vs. SQLite

System Properties Comparison Dgraph vs. Infobright vs. Microsoft Azure SQL Database vs. Oracle Coherence vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Database as a Service offering with high compatibility to Microsoft SQL Server

Oracles in-memory data grid solution

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	1.92
Rank	#130	Overall
	#22	Key-value stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

dgraph.io

ignitetech.com/softwarelibrary/infobrightdb

azure.microsoft.com/en-us/products/azure-sql/database

www.oracle.com/java/coherence

www.sqlite.org

Technical documentation

dgraph.io/docs

docs.microsoft.com/en-us/azure/azure-sql

docs.oracle.com/en/middleware/standalone/coherence

www.sqlite.org/docs.html

Developer

Dgraph Labs, Inc.

Ignite Technologies Inc.; formerly InfoBright Inc.

Microsoft

Oracle

Dwayne Richard Hipp

Initial release

2016

2005

2010

2007

2000

Current release

V12

14.1, August 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

commercial

Open Source

Public Domain

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

Java

Server operating systems

Linux
OS X
Windows

Linux
Windows

hosted

All OS with a Java VM

server-less

Data scheme

schema-free

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

APIs and other access methods

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

ADO.NET
JDBC
ODBC

JCache
JPA
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

.Net
C++
Java

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

Server-side scripts

Stored procedures

Transact SQL

Triggers

yes

Live Events

yes

Partitioning methods

Methods for storing different data on different nodes

yes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Source-replica replication

yes, with always 3 replicas available

yes, with selectable consistency level

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

configurable

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

optionally

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

Planned for future releases

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

fine grained access rights according to SQL-standard

authentification to access the cache via certificates or http basic 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.