DBMS > InterSystems Caché vs. KeyDB vs. Microsoft Azure SQL Database vs. MySQL

System Properties Comparison InterSystems Caché vs. KeyDB vs. Microsoft Azure SQL Database vs. MySQL

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

A multi-model DBMS and application server

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

Database as a Service offering with high compatibility to Microsoft SQL Server

Widely used open source RDBMS

Primary database model

Key-value store
Object oriented DBMS
Relational DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS

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

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

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

www.intersystems.com/products/cache

github.com/Snapchat/KeyDB
keydb.dev

azure.microsoft.com/en-us/products/azure-sql/database

www.mysql.com

Technical documentation

docs.intersystems.com

docs.keydb.dev

docs.microsoft.com/en-us/azure/azure-sql

dev.mysql.com/doc

Developer

InterSystems

EQ Alpha Technology Ltd.

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

1997

2019

2010

1995

Current release

2018.1.4, May 2020

V12

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

BSD-3

commercial

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

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

Linux

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

depending on used data model

schema-free

yes

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

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

.NET Client API
JDBC
ODBC
RESTful HTTP API

Proprietary protocol

RESP - REdis Serialization Protoco

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

Transact SQL

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

yes, with always 3 replicas available

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

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

Access rights for users, groups and roles

simple password-based access control and ACL

fine grained access rights according to SQL-standard

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.