DBMS > Couchbase vs. Datomic vs. GBase vs. Ignite vs. SiteWhere

System Properties Comparison Couchbase vs. Datomic vs. GBase vs. Ignite vs. SiteWhere

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

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

M2M integration platform for persisting/querying time series data

Primary database model

Document store

Relational DBMS

Key-value store
Relational DBMS

Time Series DBMS

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

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

Score	17.30
Rank	#36	Overall
	#5	Document stores

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	1.07
Rank	#185	Overall
	#86	Relational DBMS

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

github.com/sitewhere/sitewhere

Technical documentation

docs.couchbase.com

docs.datomic.com

apacheignite.readme.io/docs

sitewhere1.sitewhere.io/index.html

Developer

Couchbase, Inc.

Cognitect

General Data Technology Co., Ltd.

Apache Software Foundation

SiteWhere

Initial release

2011

2012

2004

2015

2010

Current release

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

1.0.6735, June 2023

GBase 8a, GBase 8s, GBase 8c

Apache Ignite 2.6

License

Commercial or Open Source

Open Source

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

commercial

limited edition free

commercial

Open Source

Apache 2.0

Open Source

Common Public Attribution License Version 1.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, Clojure

C, Java, Python

C++, Java, .Net

Java

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

Linux

Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

predefined scheme

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.

yes

Secondary indexes

yes

SQL

Support of SQL

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

Standard with numerous extensions

ANSI-99 for query and DML statements, subset of DDL

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

RESTful HTTP API

ADO.NET
C API
JDBC
ODBC

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

HTTP REST

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

Clojure
Java

C#
C++
Java
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

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

yes

Transaction Functions

user defined functions

yes (compute grid and cache interceptors can be used instead)

Triggers

yes

via the TAP protocol

By using transaction functions

yes

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

none

But extensive use of caching in the application peers

horizontal partitioning (by range, list and hash) and vertical partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

none

But extensive use of caching in the application peers

yes

yes (replicated cache)

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

Ephemeral buckets

yes

recommended only for testing and development

yes

User concepts

Access control

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

yes

Security Hooks for custom implementations

Users with fine-grained authorization concept

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.