DBMS > EJDB vs. Ignite vs. QuestDB vs. RocksDB

System Properties Comparison EJDB vs. Ignite vs. QuestDB vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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 high performance open source SQL database for time series data

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Document store

Key-value store
Relational DBMS

Time Series DBMS

Key-value store

Secondary database models

Relational DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

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

Score	2.52
Rank	#109	Overall
	#9	Time Series DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

github.com/Softmotions/ejdb

ignite.apache.org

questdb.io

rocksdb.org

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

apacheignite.readme.io/docs

questdb.io/docs

github.com/facebook/rocksdb/wiki

Developer

Softmotions

Apache Software Foundation

QuestDB Technology Inc

Facebook, Inc.

Initial release

2012

2015

2014

2013

Current release

Apache Ignite 2.6

8.11.4, April 2024

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

BSD

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.

Implementation language

C++, Java, .Net

Java (Zero-GC), C++, Rust

C++

Server operating systems

server-less

Linux
OS X
Solaris
Windows

Linux
macOS
Windows

Linux

Data scheme

schema-free

yes

schema-free via InfluxDB Line Protocol

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

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

SQL with time-series extensions

APIs and other access methods

in-process shared library

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

C++ API
Java API

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C#
C++
Java
PHP
Python
Ruby
Scala

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

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

Triggers

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning (by timestamps)

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes (replicated cache)

Source-replica replication with eventual consistency

yes

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

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

ACID

ACID for single-table writes

yes

Concurrency

Support for concurrent manipulation of data

yes

Read/Write 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

through memory mapped files

yes

User concepts

Access control

Security Hooks for custom implementations

More information provided by the system vendor

Specific characteristics

Relational model with native time series support Column-based storage and time partitioned...
» more

Competitive advantages

High ingestion throughput: peak of 4M rows/sec (TSBS Benchmark) Code optimizations...
» more

Typical application scenarios

Financial tick data Industrial IoT Application Metrics Monitoring
» more

Key customers

Banks & Hedge funds, Yahoo, OKX, Airbus, Aquis Exchange, Net App, Cloudera, Airtel,...
» more

Licensing and pricing models

Open source Apache 2.0 QuestDB Enterprise QuestDB Cloud
» more

News

Does "vpmovzxbd" Scare You? Here's Why it Doesn't Have To
12 April 2024

Create an ADS-B flight radar with QuestDB and a Raspberry Pi
8 April 2024

Build a temperature IoT sensor with Raspberry Pi Pico & QuestDB
5 April 2024

Create an IoT server with QuestDB and a Raspberry Pi
4 April 2024

TimescaleDB vs. QuestDB: Performance benchmarks and overview
27 March 2024

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.