DBMS > Dgraph vs. GeoMesa vs. OrientDB vs. PouchDB vs. SQLite

System Properties Comparison Dgraph vs. GeoMesa vs. OrientDB vs. PouchDB vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Multi-model DBMS (Document, Graph, Key/Value)

JavaScript DBMS with an API inspired by CouchDB

Widely used embeddable, in-process RDBMS

Primary database model

Graph DBMS

Spatial DBMS

Document store
Graph DBMS
Key-value store

Document store

Relational DBMS

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

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	3.25
Rank	#89	Overall
	#16	Document stores
	#6	Graph DBMS
	#13	Key-value stores

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

Technical documentation

dgraph.io/docs

www.geomesa.org/documentation/stable/user/index.html

www.orientdb.com/docs/last/index.html

pouchdb.com/guides

www.sqlite.org/docs.html

Developer

Dgraph Labs, Inc.

CCRi and others

OrientDB LTD; CallidusCloud; SAP

Apache Software Foundation

Dwayne Richard Hipp

Initial release

2016

2014

2010

2012

2000

Current release

5.0.0, May 2024

3.2.29, March 2024

7.1.1, June 2019

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache License 2.0

Open Source

Apache version 2

Open Source

Public Domain

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

Scala

Java

JavaScript

Server operating systems

Linux
OS X
Windows

All OS with a Java JDK (>= JDK 6)

server-less, requires a JavaScript environment (browser, Node.js)

server-less

Data scheme

schema-free

yes

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

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.

Secondary indexes

yes

via views

yes

SQL

Support of SQL

SQL-like query language, no joins

yes

SQL-92 is not fully supported

APIs and other access methods

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

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

HTTP REST

only for PouchDB Server
JavaScript 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++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

JavaScript

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

Java, Javascript

View functions in JavaScript

Triggers

Hooks

yes

Partitioning methods

Methods for storing different data on different nodes

yes

depending on storage layer

Sharding

with a proxy-based framework, named couchdb-lounge

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

depending on storage layer

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

could be achieved with distributed queries

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Eventual Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes

In-memory capabilities

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

depending on storage layer

yes

User concepts

Access control

Planned for future releases

yes

depending on the DBMS used for storage

Access rights for users and roles; record level security configurable

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.