DBMS > KairosDB vs. LevelDB vs. PouchDB vs. searchxml vs. SQLite

System Properties Comparison KairosDB vs. LevelDB vs. PouchDB vs. searchxml vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Distributed Time Series DBMS based on Cassandra or H2

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

JavaScript DBMS with an API inspired by CouchDB

DBMS for structured and unstructured content wrapped with an application server

Widely used embeddable, in-process RDBMS

Primary database model

Time Series DBMS

Key-value store

Document store

Native XML DBMS
Search engine

Relational DBMS

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

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

Score	2.25
Rank	#115	Overall
	#19	Key-value stores

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

github.com/kairosdb/kairosdb

github.com/google/leveldb

pouchdb.com

www.searchxml.net/category/products

www.sqlite.org

Technical documentation

kairosdb.github.io

github.com/google/leveldb/blob/main/doc/index.md

pouchdb.com/guides

www.searchxml.net/support/handouts

www.sqlite.org/docs.html

Developer

Google

Apache Software Foundation

informationpartners gmbh

Dwayne Richard Hipp

Initial release

2013

2011

2012

2015

2000

Current release

1.2.2, November 2018

1.23, February 2021

7.1.1, June 2019

1.0

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

BSD

Open Source

commercial

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

C++

JavaScript

C++

Server operating systems

Linux
OS X
Windows

Illumos
Linux
OS X
Windows

server-less, requires a JavaScript environment (browser, Node.js)

Windows

server-less

Data scheme

schema-free

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

via views

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

APIs and other access methods

Graphite protocol
HTTP REST
Telnet API

HTTP REST

only for PouchDB Server
JavaScript API

RESTful HTTP API
WebDAV
XQuery
XSLT

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Java
JavaScript

Node.js
PHP
Python

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

JavaScript

C++

most other programming languages supported via APIs

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

View functions in JavaScript

yes

on the application server

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

none

Sharding

with a proxy-based framework, named couchdb-lounge

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

none

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

sychronisation to multiple collections

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

multiple readers, single writer

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

with automatic compression on writes

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

simple password-based access control

Domain, group and role-based access control at the document level and for application services

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.