DBMS > Couchbase vs. Coveo vs. HEAVY.AI vs. YottaDB

System Properties Comparison Couchbase vs. Coveo vs. HEAVY.AI vs. YottaDB

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

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

A fast and solid embedded Key-value store

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

Spatial DBMS

Relational DBMS

using the Octo plugin

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

Score	16.59
Rank	#36	Overall
	#5	Document stores

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	1.64
Rank	#145	Overall
	#67	Relational DBMS

Score	0.28
Rank	#306	Overall
	#44	Key-value stores

Website

www.couchbase.com

www.coveo.com

github.com/heavyai/heavydb
www.heavy.ai

yottadb.com

Technical documentation

docs.couchbase.com

docs.coveo.com

docs.heavy.ai

yottadb.com/resources/documentation

Developer

Couchbase, Inc.

Coveo

HEAVY.AI, Inc.

YottaDB, LLC

Initial release

2011

2012

2016

2001

Current release

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

5.10, January 2022

License

Commercial or Open Source

Open Source

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

commercial

Open Source

Apache Version 2; enterprise edition available

Open Source

AGPL 3.0

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

C++ and CUDA

Server operating systems

Linux
OS X
Windows

hosted

Linux

Docker
Linux

Data scheme

schema-free

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

yes

schema-free

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

SQL

Support of SQL

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

yes

by using the Octo plugin

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

JDBC
ODBC
Thrift
Vega

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

C#
Java
JavaScript
Python

All languages supporting JDBC/ODBC/Thrift
Python

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

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

Triggers

yes

via the TAP protocol

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

yes

Sharding

Round robin

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

yes

Multi-source replication

yes

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

yes

Transaction concepts

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

ACID

yes

optimistic locking

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.

granular access controls, API key management, content filters

fine grained access rights according to SQL-standard

Users and groups based on OS-security mechanisms

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.