DBMS > Apache Impala vs. ClickHouse vs. Drizzle vs. EDB Postgres vs. Microsoft Access

System Properties Comparison Apache Impala vs. ClickHouse vs. Drizzle vs. EDB Postgres vs. Microsoft Access

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

Analytic DBMS for Hadoop

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.

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

The EDB Postgres Platform is an enterprise-class data management platform based on the open source database PostgreSQL with flexible deployment options and Oracle compatibility features, complemented by tool kits for management, integration, and migration.

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.)

Primary database model

Relational DBMS

Secondary database models

Document store

Time Series DBMS

Document store
Spatial DBMS

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	16.34
Rank	#38	Overall
	#23	Relational DBMS

Score	1.90
Rank	#135	Overall
	#63	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Website

impala.apache.org

clickhouse.com

www.enterprisedb.com

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

Technical documentation

impala.apache.org/impala-docs.html

clickhouse.com/docs

www.enterprisedb.com/docs

developer.microsoft.com/en-us/access

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Clickhouse Inc.

Drizzle project, originally started by Brian Aker

EnterpriseDB

Microsoft

Initial release

2013

2016

2008

2005

1992

Current release

4.1.0, June 2022

v24.3.2.23-lts, April 2024

7.2.4, September 2012

14, December 2021

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache 2.0

Open Source

GNU GPL

commercial

BSD for PostgreSQL-components

commercial

Bundled with Microsoft Office

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.

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

Implementation language

C++

Server operating systems

Linux

FreeBSD
Linux
macOS

FreeBSD
Linux
OS X

Linux
Windows

Windows

Not a real database server, but making use of DLLs

Data scheme

yes

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

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

Close to ANSI SQL (SQL/JSON + extensions)

yes

with proprietary extensions

yes

standard with numerous extensions

yes

but not compliant to any SQL standard

APIs and other access methods

JDBC
ODBC

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

JDBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

ADO.NET
DAO
ODBC
OLE DB

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

.Net
C
C++
Delphi
Java
Perl
PHP
Python
Tcl

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

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

yes

since Access 2010 using the ACE-engine

Triggers

hooks for callbacks inside the server can be used.

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

key based and custom

Sharding

horizontal partitioning

by hash, list or range

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

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

Multi-source replication
Source-replica replication

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

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

based on Apache Sentry and Kerberos

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.

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

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

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.