DBMS > Coveo vs. EJDB vs. Riak KV vs. TerarkDB

System Properties Comparison Coveo vs. EJDB vs. Riak KV vs. TerarkDB

Please select another system to include it in the comparison.

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

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

Distributed, fault tolerant key-value store

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Search engine

Document store

Key-value store

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

Key-value store

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

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

www.coveo.com

github.com/Softmotions/ejdb

github.com/bytedance/terarkdb

Technical documentation

docs.coveo.com

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

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

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Coveo

Softmotions

OpenSource, formerly Basho Technologies

ByteDance, originally Terark

Initial release

2012

2009

2016

Current release

3.2.0, December 2022

License

Commercial or Open Source

commercial

Open Source

GPLv2

Open Source

Apache version 2, commercial enterprise edition

commercial

restricted open source version available

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

Erlang

C++

Server operating systems

hosted

server-less

Linux
OS X

Data scheme

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

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

restricted

SQL

Support of SQL

APIs and other access methods

RESTful HTTP API

in-process shared library

HTTP API
Native Erlang Interface

C++ API
Java API

Supported programming languages

C#
Java
JavaScript
Python

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

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++
Java

Server-side scripts

Stored procedures

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

yes

none

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

selectable replication factor

none

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

typically not needed, however similar functionality with collection joins possible

links between data sets can be stored

Transaction concepts

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

yes

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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

User concepts

Access control

granular access controls, API key management, content filters

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.

Related products and services

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

More resources

Recent citations in the news

Coveo Solutions (OTCMKTS:CVOSF) Trading Up 1.8%
25 May 2024, Defense World

Coveo Debuts GenAI Tools on Genesys Cloud and AppFoundry
17 May 2024, CX Today

Coveo Solutions Full Year 2023 Earnings: EPS Beats Expectations
24 May 2024, Yahoo Canada Shine On

Coveo Named a Leader in the 2024 Gartner® Magic Quadrant™ for Search and Product Discovery
16 May 2024, PR Newswire

Coveo to Showcase the Significant Impact of AI and GenAI to Improve Digital Experiences at 10th Edition of Relevance ...
21 March 2024, GlobeNewswire

provided by Google News

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

A Critique of Resizable Hash Tables: Riak Core & Random Slicing
26 August 2018, InfoQ.com

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

Riak Taps Mesos for 'Push Button' NoSQL Scalability
20 August 2015, Datanami

provided by Google News

Share this page