DBMS > Coveo vs. Elasticsearch vs. Heroic vs. RocksDB vs. Tibero

System Properties Comparison Coveo vs. Elasticsearch vs. Heroic vs. RocksDB vs. Tibero

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 distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

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

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	135.35
Rank	#7	Overall
	#1	Search engines

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	1.78
Rank	#140	Overall
	#64	Relational DBMS

Website

www.coveo.com

www.elastic.co/elasticsearch

github.com/spotify/heroic

rocksdb.org

us.tmaxsoft.com/products/tibero

Technical documentation

docs.coveo.com

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

spotify.github.io/heroic

github.com/facebook/rocksdb/wiki

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Coveo

Elastic

Spotify

Facebook, Inc.

TmaxSoft

Initial release

2012

2010

2014

2013

2003

Current release

8.6, January 2023

8.11.4, April 2024

6, April 2015

License

Commercial or Open Source

commercial

Open Source

Elastic License

Open Source

Apache 2.0

Open Source

BSD

commercial

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

C and Assembler

Server operating systems

hosted

All OS with a Java VM

Linux

AIX
HP-UX
Linux
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

Flexible type definitions. Once a type is defined, it is persistent

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.

yes

Secondary indexes

yes

All search fields are automatically indexed

yes

via Elasticsearch

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

RESTful HTTP API

Java API
RESTful HTTP/JSON API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

C++ API
Java API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

C#
Java
JavaScript
Python

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

yes

Persistent Stored Procedure (PSM)

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

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.

Memcached and Redis integration

yes

planned for next version

User concepts

Access control

granular access controls, API key management, content filters

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.