DBMS > ClickHouse vs. Ignite vs. Oracle NoSQL vs. SAP SQL Anywhere vs. SiteWhere

System Properties Comparison ClickHouse vs. Ignite vs. Oracle NoSQL vs. SAP SQL Anywhere vs. SiteWhere

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.

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.

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

M2M integration platform for persisting/querying time series data

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Document store
Key-value store
Relational DBMS

Relational DBMS

Time Series DBMS

Secondary database models

Time Series DBMS

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

Score	16.34
Rank	#38	Overall
	#23	Relational DBMS

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

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

clickhouse.com

ignite.apache.org

www.oracle.com/database/nosql/technologies/nosql

www.sap.com/products/technology-platform/sql-anywhere.html

github.com/sitewhere/sitewhere

Technical documentation

clickhouse.com/docs

apacheignite.readme.io/docs

docs.oracle.com/en/database/other-databases/nosql-database/index.html

help.sap.com/docs/SAP_SQL_Anywhere

sitewhere1.sitewhere.io/index.html

Developer

Clickhouse Inc.

Apache Software Foundation

Oracle

SAP

formerly Sybase

SiteWhere

Initial release

2016

2015

2011

1992

2010

Current release

v24.4.1.2088-stable, May 2024

Apache Ignite 2.6

23.3, December 2023

17, July 2015

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

commercial

Open Source

Common Public Attribution License Version 1.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, .Net

Java

Server operating systems

FreeBSD
Linux
macOS

Linux
OS X
Solaris
Windows

Linux
Solaris SPARC/x86

AIX
HP-UX
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

predefined scheme

Typing

predefined data types such as float or date

yes

optional

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

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

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

SQL-like DML and DDL statements

yes

APIs and other access methods

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

RESTful HTTP API

ADO.NET
HTTP API
JDBC
ODBC

HTTP REST

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

C#
C++
Java
PHP
Python
Ruby
Scala

C
C#
Go
Java
JavaScript (Node.js)
Python

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

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

yes, in C/C++, Java, .Net or Perl

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

key based and custom

Sharding

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

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

yes (replicated cache)

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

Source-replica replication

Database mirroring

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

configurable

ACID within a storage node (=shard)

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

off heap cache

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.

Security Hooks for custom implementations

Access rights for users and roles

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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.