DBMS > Dgraph vs. Geode vs. IRONdb vs. Spark SQL vs. SQLite

System Properties Comparison Dgraph vs. Geode vs. IRONdb vs. Spark SQL vs. SQLite

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Distributed and scalable native Graph DBMS

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Spark SQL is a component on top of 'Spark Core' for structured data processing

Widely used embeddable, in-process RDBMS

Primary database model

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

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

dgraph.io

geode.apache.org

www.circonus.com/solutions/time-series-database/

spark.apache.org/sql

www.sqlite.org

Technical documentation

dgraph.io/docs

geode.apache.org/docs

docs.circonus.com/irondb/category/getting-started

spark.apache.org/docs/latest/sql-programming-guide.html

www.sqlite.org/docs.html

Developer

Dgraph Labs, Inc.

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Circonus LLC.

Apache Software Foundation

Dwayne Richard Hipp

Initial release

2016

2002

2017

2014

2000

Current release

1.1, February 2017

V0.10.20, January 2018

3.5.0 ( 2.13), September 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

Apache 2.0

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

Java

C and C++

Scala

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

the JDK (8 or later) is also required

Linux

Linux
OS X
Windows

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

SQL

Support of SQL

SQL-like query language (OQL)

SQL-like query language (Circonus Analytics Query Language: CAQL)

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

Java Client API
Memcached protocol
RESTful HTTP API

HTTP API

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

.Net
All JVM based languages
C++
Groovy
Java
Scala

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

Java
Python
R
Scala

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

user defined functions

yes, in Lua

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

Automatic, metric affinity per node

yes, utilizing Spark Core

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Multi-source replication

configurable replication factor, datacenter aware

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 per node, eventual consistency across nodes

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

User concepts

Access control

Planned for future releases

Access rights per client and object definable

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.