DBMS > Coveo vs. InterSystems Caché vs. KeyDB vs. Snowflake

System Properties Comparison Coveo vs. InterSystems Caché vs. KeyDB vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Caché is a deprecated database engine which is substituted with InterSystems IRIS. It therefore is removed from the DB-Engines Ranking.

Description

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

A multi-model DBMS and application server

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

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Search engine

Key-value store
Object oriented DBMS
Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Document store

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

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	0.71
Rank	#226	Overall
	#33	Key-value stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.coveo.com

www.intersystems.com/products/cache

github.com/Snapchat/KeyDB
keydb.dev

www.snowflake.com

Technical documentation

docs.coveo.com

docs.intersystems.com

docs.keydb.dev

docs.snowflake.net/manuals/index.html

Developer

Coveo

InterSystems

EQ Alpha Technology Ltd.

Snowflake Computing Inc.

Initial release

2012

1997

2019

2014

Current release

2018.1.4, May 2020

License

Commercial or Open Source

commercial

Open Source

BSD-3

commercial

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

Server operating systems

hosted

AIX
HP Open VMS
HP-UX
Linux
OS X
Solaris
Windows

Linux

hosted

Data scheme

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

depending on used data model

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

yes

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

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP API

.NET Client API
JDBC
ODBC
RESTful HTTP API

Proprietary protocol

RESP - REdis Serialization Protoco

CLI Client
JDBC
ODBC

Supported programming languages

C#
Java
JavaScript
Python

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Lua

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

yes

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication
Source-replica replication

yes

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

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

Concurrency

Support for concurrent manipulation of data

yes

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 for users, groups and roles

simple password-based access control and ACL

Users with fine-grained authorization concept, user roles and pluggable authentication

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.