DBMS > Geode vs. MarkLogic vs. RDFox vs. SQLite

System Properties Comparison Geode vs. MarkLogic vs. RDFox vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Operational and transactional Enterprise NoSQL database

High performance knowledge graph and semantic reasoning engine

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Graph DBMS
RDF store

Relational DBMS

Secondary database models

Relational DBMS

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

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

Score	4.15
Rank	#70	Overall
	#11	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#8	Search engines

Score	0.22
Rank	#305	Overall
	#25	Graph DBMS
	#15	RDF stores

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

geode.apache.org

www.progress.com/marklogic

www.oxfordsemantic.tech

www.sqlite.org

Technical documentation

geode.apache.org/docs

www.progress.com/marklogic/documentation

docs.oxfordsemantic.tech

www.sqlite.org/docs.html

Developer

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

MarkLogic Corp.

Oxford Semantic Technologies

Dwayne Richard Hipp

Initial release

2002

2001

2017

2000

Current release

1.1, February 2017

11.0, December 2022

6.0, Septermber 2022

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

restricted free version is available

commercial

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

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux
OS X
Windows

Linux
macOS
Windows

server-less

Data scheme

schema-free

Schema can be enforced

yes

RDF schemas

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

SQL

Support of SQL

SQL-like query language (OQL)

yes

SQL92

yes

SQL-92 is not fully supported

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

RESTful HTTP API
SPARQL 1.1

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

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

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

user defined functions

yes

via XQuery or JavaScript

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

replication via a shared file system

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Immediate Consistency in stand-alone mode, Eventual Consistency in replicated setups

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

ACID

can act as a resource manager in an XA/JTA transaction

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

yes, with Range Indexes

yes

User concepts

Access control

Access rights per client and object definable

Role-based access control at the document and subdocument levels

Roles, resources, and access types

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.