DBMS > Amazon Redshift vs. ClickHouse vs. Ignite vs. Microsoft Access vs. RavenDB

System Properties Comparison Amazon Redshift vs. ClickHouse vs. Ignite vs. Microsoft Access vs. RavenDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A high-performance, column-oriented SQL DBMS for online analytical processing (OLAP) that uses all available system resources to their full potential to process each analytical query as fast as possible. It is available as both an open-source software and a cloud offering.

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Document store

Secondary database models

Time Series DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	16.34
Rank	#38	Overall
	#23	Relational DBMS

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Website

aws.amazon.com/redshift

clickhouse.com

ignite.apache.org

www.microsoft.com/en-us/microsoft-365/access

ravendb.net

Technical documentation

docs.aws.amazon.com/redshift

clickhouse.com/docs

apacheignite.readme.io/docs

developer.microsoft.com/en-us/access

ravendb.net/docs

Developer

Amazon (based on PostgreSQL)

Clickhouse Inc.

Apache Software Foundation

Microsoft

Hibernating Rhinos

Initial release

2012

2016

2015

1992

2010

Current release

v24.4.1.2088-stable, May 2024

Apache Ignite 2.6

1902 (16.0.11328.20222), March 2019

5.4, July 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache 2.0

commercial

Bundled with Microsoft Office

Open Source

AGPL version 3, commercial license 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.

ClickHouse Cloud: Get the performance you love from open source ClickHouse in a serverless offering that takes care of the details so you can spend more time getting insight out of the fastest database on earth.
Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.
DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.

Implementation language

C++

C++, Java, .Net

C++

Server operating systems

hosted

FreeBSD
Linux
macOS

Linux
OS X
Solaris
Windows

Windows

Not a real database server, but making use of DLLs

Linux
macOS
Raspberry Pi
Windows

Data scheme

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.

yes

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

Close to ANSI SQL (SQL/JSON + extensions)

ANSI-99 for query and DML statements, subset of DDL

yes

but not compliant to any SQL standard

SQL-like query language (RQL)

APIs and other access methods

JDBC
ODBC

gRPC
HTTP REST
JDBC
MySQL wire protocol
ODBC
PostgreSQL wire protocol
Proprietary protocol

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

ADO.NET
DAO
ODBC
OLE DB

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

3rd party library
C++
Elixir

3rd party library
Go

3rd party library
Java

3rd party library
JavaScript (Node.js)

3rd party library
Kotlin

3rd party library
Nim

3rd party library
Perl

3rd party library
PHP

3rd party library
Python

3rd party library
R

3rd party library
Ruby

3rd party library
Rust
Scala

3rd party library

C#
C++
Java
PHP
Python
Ruby
Scala

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

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

Server-side scripts

Stored procedures

user defined functions

in Python

yes

yes (compute grid and cache interceptors can be used instead)

yes

since Access 2010 using the ACE-engine

yes

Triggers

yes (cache interceptors and events)

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

key based and custom

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Asynchronous and synchronous physical replication; geographically distributed replicas; support for object storages.

yes (replicated cache)

none

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

but no files for transaction logging

ACID, Cluster-wide transaction available

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

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 and roles. Column and row based policies. Quotas and resource limits. Pluggable authentication with LDAP and Kerberos. Password based, X.509 certificate, and SSH key authentication.

Security Hooks for custom implementations

a simple user-level security was built in till version Access 2003

Authorization levels configured per client per database

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.