DBMS > Coveo vs. Drizzle vs. GeoSpock vs. Riak TS vs. RocksDB

System Properties Comparison Coveo vs. Drizzle vs. GeoSpock vs. Riak TS vs. RocksDB

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.

GeoSpock seems to be discontinued. Therefore it will be 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.

Spatial and temporal data processing engine for extreme data scale

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

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

Primary database model

Secondary database models

Time Series DBMS

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

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

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

Website

www.coveo.com

geospock.com

rocksdb.org

Technical documentation

docs.coveo.com

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

github.com/facebook/rocksdb/wiki

Developer

Coveo

Drizzle project, originally started by Brian Aker

GeoSpock

Open Source, formerly Basho Technologies

Facebook, Inc.

Initial release

2012

2008

2015

2013

Current release

7.2.4, September 2012

2.0, September 2019

3.0.0, September 2022

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

GNU GPL

commercial

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

C++

Java, Javascript

Erlang

C++

Server operating systems

hosted

FreeBSD
Linux
OS X

hosted

Linux
OS X

Linux

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

temporal, categorical

restricted

SQL

Support of SQL

yes

with proprietary extensions

ANSI SQL for query only (using Presto)

yes, limited

APIs and other access methods

RESTful HTTP API

JDBC

HTTP API
Native Erlang Interface

C++ API
Java API

Supported programming languages

C#
Java
JavaScript
Python

C
C++
Java
PHP

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

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

Automatic sharding

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica 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

links between datasets can be stored

Transaction concepts

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

yes

ACID

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

User concepts

Access control

granular access controls, API key management, content filters

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users can be defined per table

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.