DBMS > Elasticsearch vs. KairosDB vs. OpenQM vs. SQLite

System Properties Comparison Elasticsearch vs. KairosDB vs. OpenQM vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

Distributed Time Series DBMS based on Cassandra or H2

QpenQM is a high-performance, self-tuning, multi-value DBMS

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	128.79
Rank	#8	Overall
	#1	Search engines

Score	0.60
Rank	#238	Overall
	#20	Time Series DBMS

Score	0.28
Rank	#291	Overall
	#10	Multivalue DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

www.elastic.co/elasticsearch

github.com/kairosdb/kairosdb

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

www.sqlite.org

Technical documentation

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

kairosdb.github.io

www.sqlite.org/docs.html

Developer

Elastic

Rocket Software, originally Martin Phillips

Dwayne Richard Hipp

Initial release

2010

2013

1993

2000

Current release

8.6, January 2023

1.2.2, November 2018

3.4-12

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

Open Source

Elastic License

Open Source

Apache 2.0

Open Source

GPLv2, extended commercial license available

Open Source

Public Domain

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

Java

Server operating systems

All OS with a Java VM

Linux
OS X
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

server-less

Data scheme

schema-free

Flexible type definitions. Once a type is defined, it is persistent

schema-free

yes

with some exceptions

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

Java API
RESTful HTTP/JSON API

Graphite protocol
HTTP REST
Telnet API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

Java
JavaScript

Node.js
PHP
Python

.Net
Basic
C
Java
Objective C
PHP
Python

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on Cassandra

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

via file-system locks

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.

Memcached and Redis integration

yes

User concepts

Access control

simple password-based access control

Access rights can be defined down to the item level

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.