DBMS > Couchbase vs. Geode vs. H2GIS vs. Trafodion

System Properties Comparison Couchbase vs. Geode vs. H2GIS vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

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

Spatial extension of H2

Transactional SQL-on-Hadoop DBMS

Primary database model

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector DBMS

Relational DBMS

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

Score	18.46
Rank	#36	Overall
	#5	Document stores

Score	1.99
Rank	#133	Overall
	#23	Key-value stores

Score	0.05
Rank	#372	Overall
	#7	Spatial DBMS

Website

Technical documentation

docs.couchbase.com

geode.apache.org/docs

www.h2gis.org/docs/home

trafodion.apache.org/documentation.html

Developer

Couchbase, Inc.

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

CNRS

Apache Software Foundation, originally developed by HP

Initial release

2011

2002

2013

2014

Current release

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

1.1, February 2017

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

LGPL 3.0

Open Source

Apache 2.0

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, C++, Go and Erlang

Java

C++, Java

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

the JDK (8 or later) is also required

Linux

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

SQL

Support of SQL

SQL++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

SQL-like query language (OQL)

yes

APIs and other access methods

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

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

Java

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

user defined functions

yes

based on H2

Java Stored Procedures

Triggers

yes

via the TAP protocol

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

Multi-source replication

yes

based on H2

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Eventual Consistency

Immediate 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

yes, multi-version concurrency control (MVCC)

yes

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

Ephemeral buckets

yes

User concepts

Access control

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base access control.

Access rights per client and object definable

yes

based on H2

fine grained access rights according to SQL-standard

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.