DBMS > Couchbase vs. Heroic vs. Kingbase vs. OrigoDB

System Properties Comparison Couchbase vs. Heroic vs. Kingbase 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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

An enterprise-class RDBMS compatible with PostgreSQL and Oracle and widely used in China.

A fully ACID in-memory object graph database

Primary database model

Document store

Time Series DBMS

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

Document store
Spatial DBMS

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

Score	16.74
Rank	#33	Overall
	#5	Document stores

Score	0.13
Rank	#335	Overall
	#29	Time Series DBMS

Score	0.44
Rank	#258	Overall
	#117	Relational DBMS

Score	0.00
Rank	#385	Overall
	#54	Document stores
	#21	Object oriented DBMS

Website

www.couchbase.com

github.com/spotify/heroic

www.kingbase.com.cn

origodb.com

Technical documentation

docs.couchbase.com

spotify.github.io/heroic

origodb.com/docs

Developer

Couchbase, Inc.

Spotify

BeiJing KINGBASE Information technologies inc.

Robert Friberg et al

Initial release

2011

2014

1999

2009

under the name LiveDB

Current release

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

V8.0, August 2021

License

Commercial or Open Source

Open Source

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

Open Source

Apache 2.0

commercial

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

C, C++, Go and Erlang

Java

C and Java

Server operating systems

Linux
OS X
Windows

Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

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.

yes

can be achieved using .NET

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

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

Standard with numerous extensions

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

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET
gokb
JDBC
kdbndp
ODBC
PDI
PDO
Pro*C
psycopg2
QT

.NET Client API
HTTP API
LINQ

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

.Net
C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

.Net

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

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

Sharding

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

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

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

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

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

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.