DBMS > ClickHouse vs. IBM Cloudant vs. SiteWhere

System Properties Comparison ClickHouse vs. IBM Cloudant vs. SiteWhere

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.

Database as a Service offering based on Apache CouchDB

M2M integration platform for persisting/querying time series data

Primary database model

Relational DBMS

Document store

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	2.68
Rank	#106	Overall
	#20	Document stores

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

clickhouse.com

www.ibm.com/products/cloudant

github.com/sitewhere/sitewhere

Technical documentation

clickhouse.com/docs

cloud.ibm.com/docs/Cloudant

sitewhere1.sitewhere.io/index.html

Developer

Clickhouse Inc.

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

SiteWhere

Initial release

2016

2010

Current release

v24.3.2.23-lts, April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Common Public Attribution License Version 1.0

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.

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

Erlang

Java

Server operating systems

FreeBSD
Linux
macOS

hosted

Linux
OS X
Windows

Data scheme

yes

schema-free

predefined scheme

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.

Secondary indexes

yes

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

APIs and other access methods

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

RESTful HTTP/JSON API

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#
Java
JavaScript
Objective-C
PHP
Ruby

Server-side scripts

Stored procedures

yes

View functions (Map-Reduce) in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

key based and custom

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.

Multi-source replication
Source-replica replication

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

atomic operations within a document possible

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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.

Access rights for users can be defined per database

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.