DBMS > Coveo vs. HEAVY.AI vs. OrigoDB vs. Riak KV vs. RocksDB

System Properties Comparison Coveo vs. HEAVY.AI vs. OrigoDB vs. Riak KV vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

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 fully ACID in-memory object graph database

Distributed, fault tolerant key-value store

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Search engine

Relational DBMS

Document store
Object oriented DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Key-value store

Secondary database models

Spatial DBMS

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

Score	2.34
Rank	#117	Overall
	#11	Search engines

Score	2.10
Rank	#126	Overall
	#61	Relational DBMS

Score	0.03
Rank	#378	Overall
	#51	Document stores
	#18	Object oriented DBMS

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Website

www.coveo.com

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

origodb.com

rocksdb.org

Technical documentation

docs.coveo.com

docs.heavy.ai

origodb.com/docs

www.tiot.jp/riak-docs/riak/kv/latest

github.com/facebook/rocksdb/wiki

Developer

Coveo

HEAVY.AI, Inc.

Robert Friberg et al

OpenSource, formerly Basho Technologies

Facebook, Inc.

Initial release

2012

2016

2009

under the name LiveDB

2009

2013

Current release

5.10, January 2022

3.2.0, December 2022

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

Open Source

Apache version 2, commercial enterprise edition

Open Source

BSD

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++ and CUDA

Erlang

C++

Server operating systems

hosted

Linux

Linux
Windows

Linux
OS X

Linux

Data scheme

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

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

restricted

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP API

JDBC
ODBC
Thrift
Vega

.NET Client API
HTTP API
LINQ

HTTP API
Native Erlang Interface

C++ API
Java API

Supported programming languages

C#
Java
JavaScript
Python

All languages supporting JDBC/ODBC/Thrift
Python

.Net

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Erlang

Triggers

yes

Domain Events

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

Round robin

horizontal partitioning

client side managed; servers are not synchronized

Sharding

no "single point of failure"

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

Source-replica replication

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

depending on model

links between data sets can be stored

Transaction concepts

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

yes

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

granular access controls, API key management, content filters

fine grained access rights according to SQL-standard

Role based authorization

yes, using Riak Security

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.