DBMS > Coveo vs. MySQL vs. Splice Machine vs. TimesTen vs. ToroDB

System Properties Comparison Coveo vs. MySQL vs. Splice Machine vs. TimesTen vs. ToroDB

Editorial information provided by DB-Engines

Name

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

Widely used open source RDBMS

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

An in-memory SQL relational database that delivers microsecond response and high throughput for OLTP applications. TimesTen can be deployed as a standalone database or as a cache to a backend Oracle database.

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Search engine

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Document store

Secondary database models

Document store
Spatial DBMS

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

Score	2.14
Rank	#116	Overall
	#11	Search engines

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.54
Rank	#244	Overall
	#114	Relational DBMS

Score	1.26
Rank	#164	Overall
	#75	Relational DBMS

Website

www.coveo.com

www.mysql.com

splicemachine.com

www.oracle.com/database/technologies/related/timesten.html

github.com/torodb/server

Technical documentation

docs.coveo.com

dev.mysql.com/doc

splicemachine.com/how-it-works

docs.oracle.com/en/database/other-databases/timesten/index.html

Developer

Coveo

Oracle

since 2010, originally MySQL AB, then Sun

Splice Machine

Oracle

originally founded in HP Labs it was acquired by Oracle in 2005

8Kdata

Initial release

2012

1995

2014

1998

2016

Current release

9.0.0, July 2024

3.1, March 2021

Release 22.1

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

AGPL 3.0, commercial license available

commercial

Open Source

AGPL-V3

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

Java

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

IBM AIX Power PC 64-bit
Linux arm64
Linux x86-64
Solaris SPARC 64
Solaris SPARC/x86
Solaris x86-64

All OS with a Java 7 VM

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

string, integer, double, boolean, date, object_id

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

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
Native Spark Datasource
ODBC

ODBC
ODP.NET
Oracle Call Interface (OCI)
Pro*C/C++ programming interfaces
SQL and PL/SQL via JDBC

Supported programming languages

C#
Java
JavaScript
Python

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

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

C
C++
Java
Node.js
PL/SQL
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Java

PL/SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Shared Nothhing Auto-Sharding, Columnar Partitioning

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

yes

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

by means of logfiles and checkpoints

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

Users with fine-grained authorization concept

no user groups or roles

Access rights for users, groups and roles according to SQL-standard

fine grained access rights according to SQL-standard

Access rights for users and 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.