DBMS > ClickHouse vs. Ingres vs. Oracle Berkeley DB vs. SwayDB

System Properties Comparison ClickHouse vs. Ingres vs. Oracle Berkeley DB vs. SwayDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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.

Well established RDBMS

Widely used in-process key-value store

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Key-value store

Secondary database models

Time Series DBMS

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

Score	15.55
Rank	#38	Overall
	#23	Relational DBMS

Score	3.80
Rank	#82	Overall
	#44	Relational DBMS

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	0.04
Rank	#387	Overall
	#61	Key-value stores

Website

clickhouse.com

www.actian.com/databases/ingres

www.oracle.com/database/technologies/related/berkeleydb.html

swaydb.simer.au

Technical documentation

clickhouse.com/docs

docs.actian.com/ingres

docs.oracle.com/cd/E17076_05/html/index.html

Developer

Clickhouse Inc.

Actian Corporation

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Simer Plaha

Initial release

2016

1974

originally developed at University Berkely in early 1970s

1994

2018

Current release

v24.4.1.2088-stable, May 2024

11.2, May 2022

18.1.40, May 2020

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

commercial license available

Open Source

GNU Affero GPL V3.0

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.
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.
DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.

Implementation language

C++

C, Java, C++ (depending on the Berkeley DB edition)

Scala

Server operating systems

FreeBSD
Linux
macOS

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
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.

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

yes

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

yes

SQL interfaced based on SQLite is available

APIs and other access methods

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

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

Supported programming languages

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

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Java
Kotlin
Scala

Server-side scripts

Stored procedures

yes

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

key based and custom

horizontal partitioning

Ingres Star to access multiple databases simultaneously

none

Replication methods

Methods for redundantly storing data on multiple nodes

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

Ingres Replicator

Source-replica replication

none

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

Transaction concepts

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

ACID

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

MVCC

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

fine grained access rights according to SQL-standard

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.