DBMS > CouchDB vs. GeoSpock vs. JanusGraph vs. SAP HANA

System Properties Comparison CouchDB vs. GeoSpock vs. JanusGraph vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

Spatial and temporal data processing engine for extreme data scale

A Graph DBMS optimized for distributed clusters

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

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Secondary database models

Spatial DBMS

using the Geocouch extension

Time Series DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

couchdb.apache.org

geospock.com

janusgraph.org

www.sap.com/products/hana.html

Technical documentation

docs.couchdb.org/en/stable

docs.janusgraph.org

help.sap.com/hana

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

GeoSpock

Linux Foundation; originally developed as Titan by Aurelius

SAP

Initial release

2005

2017

2010

Current release

3.3.3, December 2023

2.0, September 2019

0.6.3, February 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Open Source

Apache 2.0

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Erlang

Java, Javascript

Java

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

hosted

Linux
OS X
Unix
Windows

Appliance or cloud-service

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

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

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

APIs and other access methods

RESTful HTTP/JSON API

JDBC

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

JDBC
ODBC

Supported programming languages

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

Clojure
Java
Python

Server-side scripts

Stored procedures

View functions in JavaScript

yes

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Automatic sharding

yes

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

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

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

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Durability

Support for making data persistent

yes

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

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

Access rights for users can be defined per database

Access rights for users can be defined per table

User authentification and security via Rexster Graph Server

yes

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.