DBMS > ClickHouse vs. SpatiaLite vs. Tkrzw vs. ToroDB

System Properties Comparison ClickHouse vs. SpatiaLite vs. Tkrzw vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

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.

Spatial extension of SQLite

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Secondary database models

Time Series DBMS

Relational DBMS

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

Score	15.88
Rank	#37	Overall
	#22	Relational DBMS

Score	1.56
Rank	#142	Overall
	#3	Spatial DBMS

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Website

clickhouse.com

www.gaia-gis.it/fossil/libspatialite/index

dbmx.net/tkrzw

github.com/torodb/server

Technical documentation

clickhouse.com/docs

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

Clickhouse Inc.

Alessandro Furieri

Mikio Hirabayashi

8Kdata

Initial release

2016

2008

2020

2016

Current release

v24.6.2.17-stable, July 2024

5.0.0, August 2020

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

Open Source

Apache Version 2.0

Open Source

AGPL-V3

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.

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

Java

Server operating systems

FreeBSD
Linux
macOS

server-less

Linux
macOS

All OS with a Java 7 VM

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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)

yes

APIs and other access methods

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

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
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

key based and custom

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

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

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

using specific database classes

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 and roles

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.