DBMS > Coveo vs. Drizzle vs. MySQL vs. Riak TS

System Properties Comparison Coveo vs. Drizzle vs. MySQL vs. Riak TS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

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

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Widely used open source RDBMS

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Primary database model

Search engine

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Website

www.coveo.com

www.mysql.com

Technical documentation

docs.coveo.com

dev.mysql.com/doc

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

Developer

Coveo

Drizzle project, originally started by Brian Aker

Oracle

since 2010, originally MySQL AB, then Sun

Open Source, formerly Basho Technologies

Initial release

2012

2008

1995

2015

Current release

7.2.4, September 2012

8.4.0, April 2024

3.0.0, September 2022

License

Commercial or Open Source

commercial

Open Source

GNU GPL

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

C and C++

Erlang

Server operating systems

hosted

FreeBSD
Linux
OS X

FreeBSD
Linux
OS X
Solaris
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.

yes

Secondary indexes

yes

restricted

SQL

Support of SQL

yes

with proprietary extensions

yes

with proprietary extensions

yes, limited

APIs and other access methods

RESTful HTTP API

JDBC

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API
Native Erlang Interface

Supported programming languages

C#
Java
JavaScript
Python

C
C++
Java
PHP

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

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

yes

proprietary syntax

Erlang

Triggers

yes

hooks for callbacks inside the server can be used.

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

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

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

links between datasets can be stored

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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.