DBMS > Coveo vs. KairosDB vs. MySQL vs. TerarkDB

System Properties Comparison Coveo vs. KairosDB vs. MySQL 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

Distributed Time Series DBMS based on Cassandra or H2

Widely used open source RDBMS

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

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Key-value store

Secondary database models

Document store
Spatial DBMS

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

Score	2.14
Rank	#116	Overall
	#11	Search engines

Score	0.60
Rank	#238	Overall
	#20	Time Series DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Website

www.coveo.com

github.com/kairosdb/kairosdb

www.mysql.com

github.com/bytedance/terarkdb

Technical documentation

docs.coveo.com

kairosdb.github.io

dev.mysql.com/doc

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Coveo

Oracle

since 2010, originally MySQL AB, then Sun

ByteDance, originally Terark

Initial release

2012

2013

1995

2016

Current release

1.2.2, November 2018

9.0.0, July 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

Java

C and C++

C++

Server operating systems

hosted

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

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

schema-free

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP API

Graphite protocol
HTTP REST
Telnet API

ADO.NET
JDBC
ODBC
Proprietary native API

C++ API
Java API

Supported programming languages

C#
Java
JavaScript
Python

Java
JavaScript

Node.js
PHP
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C++
Java

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

based on Cassandra

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on Cassandra

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

yes

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

simple password-based access control

Users with fine-grained authorization concept

no user groups or roles

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.