DBMS > Couchbase vs. Infobright vs. Warp 10 vs. Yaacomo

System Properties Comparison Couchbase vs. Infobright vs. Warp 10 vs. Yaacomo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

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

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

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

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

Score	16.59
Rank	#36	Overall
	#5	Document stores

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

www.couchbase.com

ignitetech.com/softwarelibrary/infobrightdb

www.warp10.io

yaacomo.com

Technical documentation

docs.couchbase.com

www.warp10.io/content/02_Getting_started

Developer

Couchbase, Inc.

Ignite Technologies Inc.; formerly InfoBright Inc.

SenX

Q2WEB GmbH

Initial release

2011

2005

2015

2009

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

commercial

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

Open Source

Apache License 2.0

commercial

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

Server operating systems

Linux
OS X
Windows

Linux
Windows

Linux
OS X
Windows

Android
Linux
Windows

Data scheme

schema-free

yes

schema-free

yes

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.

Secondary indexes

yes

Knowledge Grid Technology used instead

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

ADO.NET
JDBC
ODBC

HTTP API
Jupyter
WebSocket

JDBC
ODBC

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

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

Server-side scripts

Stored procedures

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

yes

WarpScript

Triggers

yes

via the TAP protocol

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

none

Sharding

based on HBase

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

Source-replica replication

selectable replication factor

based on HBase

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

based on HBase

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

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

exploiting MySQL or PostgreSQL frontend capabilities

Mandatory use of cryptographic tokens, containing fine-grained authorizations

fine grained access rights according to SQL-standard

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.