DBMS > Couchbase vs. Geode vs. SingleStore vs. TigerGraph vs. XTDB

System Properties Comparison Couchbase vs. Geode vs. SingleStore vs. TigerGraph vs. XTDB

Editorial information provided by DB-Engines

Name

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

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

A general purpose database with bitemporal SQL and Datalog and graph queries

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

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

Score	16.74
Rank	#33	Overall
	#5	Document stores

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

Score	4.02
Rank	#74	Overall
	#39	Relational DBMS

Score	1.44
Rank	#152	Overall
	#14	Graph DBMS

Score	0.13
Rank	#330	Overall
	#45	Document stores

Website

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.couchbase.com

geode.apache.org/docs

docs.singlestore.com

docs.tigergraph.com

www.xtdb.com/docs

Developer

Couchbase, Inc.

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

SingleStore Inc.

Juxt Ltd.

Initial release

2011

2002

2013

2017

2019

Current release

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

1.1, February 2017

8.5, January 2024

1.19, September 2021

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

commercial

free developer edition available

commercial

Open Source

MIT License

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

C++

Clojure

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

the JDK (8 or later) is also required

Linux

64 bit version required

Linux

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

but no triggers and foreign keys

SQL-like query language (GSQL)

limited SQL, making use of Apache Calcite

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

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

HTTP REST
JDBC

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

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

Bash
C
C#
Java
JavaScript (Node.js)
Python

C++
Java

Clojure
Java

Server-side scripts

Stored procedures

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

user defined functions

yes

Triggers

yes

via the TAP protocol

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

Sharding

hash partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

Multi-source replication

Source-replica replication

stores two copies of each physical data partition on two separate nodes

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can define user-defined aggregate functions for map-reduce-style calculations

yes

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

Relationships in graphs

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

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

Fine grained access control via users, groups and roles

Role-based access control

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.