DBMS > Coveo vs. Cubrid vs. GeoMesa vs. Riak KV

System Properties Comparison Coveo vs. Cubrid vs. GeoMesa vs. Riak KV

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

CUBRID is an open-source SQL-based relational database management system with object extensions for OLTP

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Distributed, fault tolerant key-value store

Primary database model

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

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

Score	2.34
Rank	#117	Overall
	#11	Search engines

Score	1.31
Rank	#169	Overall
	#78	Relational DBMS

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

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

Website

www.coveo.com

cubrid.com (korean)
cubrid.org (english)

www.geomesa.org

Technical documentation

docs.coveo.com

cubrid.org/manuals

www.geomesa.org/documentation/stable/user/index.html

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

Developer

Coveo

CUBRID Corporation, CUBRID Foundation

CCRi and others

OpenSource, formerly Basho Technologies

Initial release

2012

2008

2014

2009

Current release

11.0, January 2021

4.0.5, February 2024

3.2.0, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Apache License 2.0

Open Source

Apache version 2, commercial enterprise edition

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

Scala

Erlang

Server operating systems

hosted

Linux
Windows

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

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

restricted

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB

HTTP API
Native Erlang Interface

Supported programming languages

C#
Java
JavaScript
Python

C
C#
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
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

Server-side scripts

Stored procedures

Java Stored Procedures

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

yes

none

depending on storage layer

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

depending on storage layer

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

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.

depending on storage layer

User concepts

Access control

granular access controls, API key management, content filters

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

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

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Closing Bell: Coveo Solutions Inc down on Monday (CVO)
22 April 2024, The Globe and Mail

AI for CX: Coveo's award-winning solution
17 April 2024, CMSWire

We're Not Worried About Coveo Solutions' (TSE:CVO) Cash Burn
20 April 2024, Simply Wall St

Research Analysts Issue Forecasts for Coveo Solutions Inc.'s Q4 2024 Earnings (TSE:CVO)
22 April 2024, MarketBeat

How Coveo delivers better experiences with generative AI by partnering with CIOs
20 October 2023, Fast Company

provided by Google News

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

Riak NoSQL Database: Use Cases and Best Practices
23 December 2011, InfoQ.com

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

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

NoSQL pioneer Basho stamps its mark on time stamp data with Riak TS
6 October 2015, The Register

provided by Google News

Share this page