DBMS > EXASOL vs. InterSystems Caché vs. JaguarDB vs. Qdrant vs. Snowflake

System Properties Comparison EXASOL vs. InterSystems Caché vs. JaguarDB vs. Qdrant vs. Snowflake

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

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

A multi-model DBMS and application server

Performant, highly scalable DBMS for AI and IoT applications

A high-performance vector database with neural network or semantic-based matching

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

Primary database model

Relational DBMS

Key-value store
Object oriented DBMS
Relational DBMS

Key-value store
Vector DBMS

Vector DBMS

Relational DBMS

Secondary database models

Document store

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

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#13	Vector DBMS

Score	1.28
Rank	#167	Overall
	#6	Vector DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.exasol.com

www.intersystems.com/products/cache

www.jaguardb.com

github.com/qdrant/qdrant
qdrant.tech

www.snowflake.com

Technical documentation

www.exasol.com/resources

docs.intersystems.com

www.jaguardb.com/support.html

qdrant.tech/documentation

docs.snowflake.net/manuals/index.html

Developer

Exasol

InterSystems

DataJaguar, Inc.

Qdrant

Snowflake Computing Inc.

Initial release

2000

1997

2015

2021

2014

Current release

2018.1.4, May 2020

3.3 July 2023

License

Commercial or Open Source

commercial

Open Source

GPL V3.0

Open Source

Apache Version 2.0

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

the server part. Clients available in other languages

Rust

Server operating systems

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

Linux

Docker
Linux
macOS
Windows

hosted

Data scheme

yes

depending on used data model

yes

schema-free

yes

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

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

.NET Client API
JDBC
ODBC
RESTful HTTP API

JDBC
ODBC

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

CLI Client
JDBC
ODBC

Supported programming languages

Java
Lua
Python
R

C#
C++
Java

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

Collection-level replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Eventual Consistency, tunable consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

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

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

Access rights for users, groups and roles

rights management via user accounts

Key-based authentication

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.