DBMS > Geode vs. ObjectBox vs. PouchDB vs. SAP HANA

System Properties Comparison Geode vs. ObjectBox vs. PouchDB vs. SAP HANA

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

Lightweight, fast on-device database for IoT, Mobile and Embedded devices, persisting and synchronising objects and vectors

JavaScript DBMS with an API inspired by CouchDB

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

Primary database model

Key-value store

Object oriented DBMS
Vector DBMS

Document store

Relational DBMS

Secondary database models

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	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	1.29
Rank	#166	Overall
	#5	Object oriented DBMS
	#7	Vector DBMS

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

geode.apache.org

github.com/objectbox
objectbox.io

pouchdb.com

www.sap.com/products/hana.html

Technical documentation

geode.apache.org/docs

docs.objectbox.io

pouchdb.com/guides

help.sap.com/hana

Developer

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

ObjectBox Limited

Apache Software Foundation

SAP

Initial release

2002

2017

2012

2010

Current release

1.1, February 2017

4.0 (May 2024)

7.1.1, June 2019

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Bindings are released under Apache 2.0

Apache License 2.0

Open Source

commercial

Cloud-based only

Only available as a cloud service

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

Java

C and C++

JavaScript

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Android
Any POSIX system
Docker
iOS
Linux
macOS
QNX
Windows

server-less, requires a JavaScript environment (browser, Node.js)

Appliance or cloud-service

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, plus "flex" map-like types

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

yes

SQL

Support of SQL

SQL-like query language (OQL)

yes

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

Proprietary native API

HTTP REST

only for PouchDB Server
JavaScript API

JDBC
ODBC

Supported programming languages

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

C
C++
Dart (Flutter)
Go
Java
Kotlin
Python
Swift

JavaScript

Server-side scripts

Stored procedures

user defined functions

View functions in JavaScript

SQLScript, R

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

with a proxy-based framework, named couchdb-lounge

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Data sync between devices allowing occasional connected databases to work completely offline

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

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

by using IndexedDB, WebSQL or LevelDB as backend

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 per client and object definable

yes

More information provided by the system vendor

News

The on-device Vector Database for Android and Java
29 May 2024

Vector search: making sense of search queries
29 May 2024

Python on-device Vector and Object Database for Local AI
28 May 2024

Evolution of search: traditional vs vector search
23 May 2024

On-device Vector Database for Dart/Flutter
21 May 2024

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.