DBMS > Couchbase vs. EJDB vs. IBM Db2 warehouse vs. OrigoDB

System Properties Comparison Couchbase vs. EJDB vs. IBM Db2 warehouse vs. OrigoDB

Please select another system to include it in the comparison.

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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Cloud-based data warehousing service

A fully ACID in-memory object graph database

Primary database model

Document store

Relational DBMS

Document store
Object oriented 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	16.59
Rank	#36	Overall
	#5	Document stores

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	1.37
Rank	#160	Overall
	#74	Relational DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Website

www.couchbase.com

github.com/Softmotions/ejdb

www.ibm.com/products/db2/warehouse

origodb.com

Technical documentation

docs.couchbase.com

github.com/Softmotions/ejdb/blob/master/README.md

origodb.com/docs

Developer

Couchbase, Inc.

Softmotions

IBM

Robert Friberg et al

Initial release

2011

2012

2014

2009

under the name LiveDB

Current release

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

License

Commercial or Open Source

Open Source

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

Open Source

GPLv2

commercial

Open Source

Cloud-based only

Only available as a cloud service

yes

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

Server operating systems

Linux
OS X
Windows

server-less

hosted

Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

User defined using .NET types and collections

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.

Import/export of XML data possible

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

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

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

in-process shared library

.NET Client API
JDBC
ODBC
OLE DB

.NET Client API
HTTP API
LINQ

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

.Net

Server-side scripts

Stored procedures

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

PL/SQL, SQL PL

yes

Triggers

yes

via the TAP protocol

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

none

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

none

yes

Source-replica replication

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

selectable on a per-operation basis

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

depending on model

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

Write ahead log

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.

fine grained access rights according to SQL-standard

Role based authorization

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.