DBMS > CouchDB vs. EJDB vs. Infobright vs. OrigoDB

System Properties Comparison CouchDB vs. EJDB vs. Infobright vs. OrigoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

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

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

A fully ACID in-memory object graph database

Primary database model

Document store

Relational DBMS

Document store
Object oriented DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

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

Website

couchdb.apache.org

github.com/Softmotions/ejdb

ignitetech.com/softwarelibrary/infobrightdb

origodb.com

Technical documentation

docs.couchdb.org/en/stable

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

origodb.com/docs

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Softmotions

Ignite Technologies Inc.; formerly InfoBright Inc.

Robert Friberg et al

Initial release

2005

2012

2005

2009

under the name LiveDB

Current release

3.3.3, December 2023

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

GPLv2

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

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

Erlang

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

server-less

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.

can be achieved using .NET

Secondary indexes

yes

via views

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP/JSON API

in-process shared library

ADO.NET
JDBC
ODBC

.NET Client API
HTTP API
LINQ

Supported programming languages

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

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

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net

Server-side scripts

Stored procedures

View functions in JavaScript

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

none

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

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

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

depending on model

Transaction concepts

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

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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

User concepts

Access control

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Couchbase climbs up the DB-Engines Ranking, increasing its popularity by 10% every month
2 June 2014, Matthias Gelbmann

show all

Recent citations in the news

How to Automate A Blog Post App Deployment With GitHub Actions, Node.js, CouchDB, and Aptible
4 December 2023, hackernoon.com

How to install the CouchDB NoSQL database on Debian Server 11
16 June 2022, TechRepublic

IBM Cloudant pulls plan to fund new foundational layer for CouchDB
15 March 2022, The Register

CouchDB 3.0 ends admin party era • DEVCLASS
27 February 2020, DevClass

Tracking Expenses with CouchDB and Angular — SitePoint
28 August 2014, SitePoint

provided by Google News

Share this page