DBMS > Dolt vs. eXtremeDB vs. Geode vs. SQLite

System Properties Comparison Dolt vs. eXtremeDB vs. Geode vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A MySQL compatible DBMS with Git-like versioning of data and schema

Natively in-memory DBMS with options for persistency, high-availability and clustering

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

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Relational DBMS
Time Series DBMS

Key-value store

Relational DBMS

Secondary database models

Document store

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

Score	0.93
Rank	#194	Overall
	#90	Relational DBMS

Score	0.79
Rank	#212	Overall
	#100	Relational DBMS
	#18	Time Series DBMS

Score	1.51
Rank	#147	Overall
	#25	Key-value stores

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

github.com/dolthub/dolt
www.dolthub.com

www.mcobject.com

geode.apache.org

www.sqlite.org

Technical documentation

docs.dolthub.com

www.mcobject.com/docs/extremedb.htm

geode.apache.org/docs

www.sqlite.org/docs.html

Developer

DoltHub Inc

McObject

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

Dwayne Richard Hipp

Initial release

2018

2001

2002

2000

Current release

8.2, 2021

1.1, February 2017

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

C and C++

Java

Server operating systems

Linux
macOS
Windows

AIX
HP-UX
Linux
macOS
Solaris
Windows

All OS with a Java VM

the JDK (8 or later) is also required

server-less

Data scheme

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.

support of XML interfaces available

Secondary indexes

yes

SQL

Support of SQL

yes

with the option: eXtremeSQL

SQL-like query language (OQL)

yes

SQL-92 is not fully supported

APIs and other access methods

CLI Client
HTTP REST

.NET Client API
JDBC
JNI
ODBC
Proprietary protocol
RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
C
C#
C++
Java
Lua
Python
Scala

.Net
All JVM based languages
C++
Groovy
Java
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

yes

currently in alpha release

yes

user defined functions

Triggers

yes

by defining events

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning / sharding

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Active Replication Fabric™ for IoT
Multi-source replication

by means of eXtremeDB Cluster option
Source-replica replication

by means of eXtremeDB High Availability option

Multi-source replication

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

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

Optimistic (MVCC) and pessimistic (locking) strategies available

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

Only one user is configurable, and must be specified in the config file at startup

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.