DBMS > Geode vs. JanusGraph vs. OpenQM vs. OrigoDB

System Properties Comparison Geode vs. JanusGraph vs. OpenQM vs. OrigoDB

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

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

QpenQM is a high-performance, self-tuning, multi-value DBMS

A fully ACID in-memory object graph database

Primary database model

Key-value store

Graph DBMS

Multivalue DBMS

Document store
Object oriented DBMS

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

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

Score	2.02
Rank	#125	Overall
	#12	Graph DBMS

Score	0.34
Rank	#284	Overall
	#10	Multivalue DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Website

geode.apache.org

janusgraph.org

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

origodb.com

Technical documentation

geode.apache.org/docs

docs.janusgraph.org

origodb.com/docs

Developer

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

Linux Foundation; originally developed as Titan by Aurelius

Rocket Software, originally Martin Phillips

Robert Friberg et al

Initial release

2002

2017

1993

2009

under the name LiveDB

Current release

1.1, February 2017

0.6.3, February 2023

3.4-12

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache 2.0

Open Source

GPLv2, extended commercial license available

Open Source

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

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux
OS X
Unix
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
Windows

Data scheme

schema-free

yes

with some exceptions

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (OQL)

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

.NET Client API
HTTP API
LINQ

Supported programming languages

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

Clojure
Java
Python

.Net
Basic
C
Java
Objective C
PHP
Python

.Net

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Cache Event Listeners

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

yes

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

depending on model

Transaction concepts

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

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

yes

Write ahead log

In-memory capabilities

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

yes

User concepts

Access control

Access rights per client and object definable

User authentification and security via Rexster Graph Server

Access rights can be defined down to the item level

Role based authorization

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

This is how much one of the most expensive gems costs at the Tucson gem show
11 February 2024, KGUN 9 Tucson News

Victor I. Cazares Wants NYTW to Call for Ceasefire in Gaza
22 February 2024, Vulture

Event-Driven Architectures with Apache Geode and Spring Integration
20 March 2019, InfoQ.com

1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode - Scaling Data Services with Pivotal ...
15 November 2018, O'Reilly Media

HPE buys query acceleration platform Ampool to boost Ezmeral hybrid cloud analytics
7 July 2021, SiliconANGLE News

provided by Google News

Database Deep Dives: JanusGraph
8 August 2019, ibm.com

JanusGraph Picks Up Where TitanDB Left Off
13 January 2017, Datanami

From graph db to graph embedding. In 7 simple steps. | by Andy Greatorex
30 July 2020, Towards Data Science

Nordstrom Builds Flexible Backend Ops with Kubernetes, Spark and JanusGraph
3 October 2019, The New Stack

Compose for JanusGraph arrives on Bluemix
15 September 2017, ibm.com

provided by Google News

Share this page