DBMS > Ingres vs. InterSystems Caché vs. MySQL vs. RocksDB

System Properties Comparison Ingres vs. InterSystems Caché vs. MySQL vs. RocksDB

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

Well established RDBMS

A multi-model DBMS and application server

Widely used open source RDBMS

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

Primary database model

Relational DBMS

Key-value store
Object oriented DBMS
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Key-value store

Secondary database models

Document store

Document store
Spatial DBMS

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

Score	3.63
Rank	#79	Overall
	#43	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	2.84
Rank	#97	Overall
	#16	Key-value stores

Website

www.actian.com/databases/ingres

www.intersystems.com/products/cache

www.mysql.com

rocksdb.org

Technical documentation

docs.actian.com/ingres

docs.intersystems.com

dev.mysql.com/doc

github.com/facebook/rocksdb/wiki

Developer

Actian Corporation

InterSystems

Oracle

since 2010, originally MySQL AB, then Sun

Facebook, Inc.

Initial release

1974

originally developed at University Berkely in early 1970s

1997

1995

2013

Current release

12.0, July 2024

2018.1.4, May 2020

9.0.0, July 2024

9.4.0, June 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

BSD

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C and C++

C++

Server operating systems

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

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

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

depending on used data model

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.

but tools for importing/exporting data from/to XML-files available

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

.NET Client API
JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

C++ API
Java API

Supported programming languages

C#
C++
Java

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Ingres Star to access multiple databases simultaneously

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Ingres Replicator

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

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

yes

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

table locks or row locks depending on storage engine

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

fine grained access rights according to SQL-standard

Access rights for users, groups and roles

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.