DBMS > Apache Kylin vs. Coveo vs. Geode vs. Machbase Neo vs. RocksDB

System Properties Comparison Apache Kylin vs. Coveo vs. Geode vs. Machbase Neo vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

A distributed analytics engine for big data, providing a SQL interface and multi-dimensional analysis (OLAP) and leveraging the Hadoop stack

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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

TimeSeries DBMS for AIoT and BigData

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

Primary database model

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

Score	1.25
Rank	#170	Overall
	#77	Relational DBMS

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

Technical documentation

kylin.apache.org/docs

docs.coveo.com

geode.apache.org/docs

machbase.com/dbms

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation, originally contributed from eBay Inc

Coveo

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Machbase

Facebook, Inc.

Initial release

2015

2012

2002

2013

Current release

3.1.0, July 2020

1.1, February 2017

V8.0, August 2023

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

free test version available

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

Java

C++

Server operating systems

Linux

hosted

All OS with a Java VM

the JDK (8 or later) is also required

Linux
macOS
Windows

Linux

Data scheme

yes

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.

Secondary indexes

yes

SQL

Support of SQL

ANSI SQL for queries (using Apache Calcite)

SQL-like query language (OQL)

SQL-like query language

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

C++ API
Java API

Supported programming languages

C#
Java
JavaScript
Python

.Net
All JVM based languages
C++
Groovy
Java
Scala

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source 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

Transaction concepts

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

yes

yes, on a single node

yes

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

volatile and lookup table

yes

User concepts

Access control

granular access controls, API key management, content filters

Access rights per client and object definable

simple password-based access control

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.