DBMS > ClickHouse vs. Ignite vs. RDF4J vs. Sphinx

System Properties Comparison ClickHouse vs. Ignite vs. RDF4J vs. Sphinx

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.

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.

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Relational DBMS

Key-value store
Relational DBMS

RDF store

Search engine

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	0.69
Rank	#230	Overall
	#9	RDF stores

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

Technical documentation

clickhouse.com/docs

apacheignite.readme.io/docs

rdf4j.org/documentation

sphinxsearch.com/docs

Developer

Clickhouse Inc.

Apache Software Foundation

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Sphinx Technologies Inc.

Initial release

2016

2015

2004

2001

Current release

v24.4.1.2088-stable, May 2024

Apache Ignite 2.6

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

GPL version 2, commercial licence available

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.

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.
Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.

Implementation language

C++

C++, Java, .Net

Java

C++

Server operating systems

FreeBSD
Linux
macOS

Linux
OS X
Solaris
Windows

Linux
OS X
Unix
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

RDF Schemas

yes

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.

yes

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

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

SQL-like query language (SphinxQL)

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

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

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#
C++
Java
PHP
Python
Ruby
Scala

Java
PHP
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes

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

yes

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

key based and custom

Sharding

none

Sharding

Partitioning is done manually, search queries against distributed index is supported

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)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

yes

The original contents of fields are not stored in the Sphinx index.

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.

Security Hooks for custom implementations

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.