DBMS > Coveo vs. jBASE vs. KeyDB vs. MySQL

System Properties Comparison Coveo vs. jBASE vs. KeyDB vs. MySQL

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

A robust multi-value DBMS comprising development tools and middleware

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Widely used open source RDBMS

Primary database model

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	1.49
Rank	#156	Overall
	#3	Multivalue DBMS

Score	0.70
Rank	#229	Overall
	#32	Key-value stores

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Website

www.coveo.com

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

github.com/Snapchat/KeyDB
keydb.dev

www.mysql.com

Technical documentation

docs.coveo.com

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

docs.keydb.dev

dev.mysql.com/doc

Developer

Coveo

Rocket Software (formerly Zumasys)

EQ Alpha Technology Ltd.

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2012

1991

2019

1995

Current release

5.7

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

BSD-3

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

Server operating systems

hosted

AIX
Linux
Windows

Linux

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

yes

Typing

predefined data types such as float or date

yes

optional

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

yes

SQL

Support of SQL

Embedded SQL for jBASE in BASIC

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP API

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

Proprietary protocol

RESP - REdis Serialization Protoco

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C#
Java
JavaScript
Python

.Net
Basic
Jabbascript
Java

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

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

Server-side scripts

Stored procedures

yes

Lua

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

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

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

yes

ACID

Optimistic locking, atomic execution of commands blocks and scripts

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

Access rights can be defined down to the item level

simple password-based access control and ACL

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.