DBMS > ClickHouse vs. Firebase Realtime Database vs. Memcached vs. ToroDB vs. VictoriaMetrics

System Properties Comparison ClickHouse vs. Firebase Realtime Database vs. Memcached vs. ToroDB vs. VictoriaMetrics

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.

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

In-memory key-value store, originally intended for caching

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

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

Primary database model

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	14.29
Rank	#39	Overall
	#6	Document stores

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	1.32
Rank	#162	Overall
	#14	Time Series DBMS

Website

clickhouse.com

firebase.google.com/products/realtime-database

www.memcached.org

github.com/torodb/server

victoriametrics.com

Technical documentation

clickhouse.com/docs

firebase.google.com/docs/database

github.com/memcached/memcached/wiki

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

Clickhouse Inc.

Google

acquired by Google 2014

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

8Kdata

VictoriaMetrics

Initial release

2016

2012

2003

2016

2018

Current release

v24.3.2.23-lts, April 2024

1.6.25, March 2024

v1.91, May 2023

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

BSD license

Open Source

AGPL-V3

Open Source

Apache Version 2.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.
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

hosted

FreeBSD
Linux
OS X
Unix
Windows

All OS with a Java 7 VM

FreeBSD
Linux
macOS
OpenBSD

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)

APIs and other access methods

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

Android
iOS
JavaScript API
RESTful HTTP API

Proprietary protocol

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

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

Java
JavaScript
Objective-C

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

limited functionality with using 'rules'

Triggers

Callbacks are triggered when data changes

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

Repcached, a Memcached patch, provides this functionallity

Source-replica replication

Synchronous 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

if the client is offline
Immediate Consistency

if the client is online

Eventual Consistency
Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

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

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.

yes, based on authentication and database rules

yes

using SASL (Simple Authentication and Security Layer) protocol

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.