DBMS > Amazon CloudSearch vs. KairosDB vs. SQLite vs. TerarkDB vs. TerminusDB

System Properties Comparison Amazon CloudSearch vs. KairosDB vs. SQLite vs. TerarkDB vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

A hosted search engine service by Amazon with the data stored in Amazons cloud

Distributed Time Series DBMS based on Cassandra or H2

Widely used embeddable, in-process RDBMS

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Secondary database models

Document store
RDF store

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

Score	1.85
Rank	#137	Overall
	#12	Search engines

Score	0.62
Rank	#239	Overall
	#20	Time Series DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

aws.amazon.com/cloudsearch

github.com/kairosdb/kairosdb

www.sqlite.org

github.com/bytedance/terarkdb

terminusdb.com

Technical documentation

docs.aws.amazon.com/cloudsearch

kairosdb.github.io

www.sqlite.org/docs.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

terminusdb.github.io/terminusdb/#

Developer

Amazon

Dwayne Richard Hipp

ByteDance, originally Terark

DataChemist Ltd.

Initial release

2012

2013

2000

2016

2018

Current release

1.2.2, November 2018

3.45.3 (15 April 2024), April 2024

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Public Domain

commercial

restricted open source version available

Open Source

GPL V3

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.

Implementation language

Java

C++

Prolog, Rust

Server operating systems

hosted

Linux
OS X
Windows

server-less

Linux

Data scheme

yes

schema-free

yes

dynamic column types

schema-free

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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.

Secondary indexes

yes

all search fields are automatically indexed

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

SQL-like query language (WOQL)

APIs and other access methods

HTTP API

Graphite protocol
HTTP REST
Telnet API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

C++ API
Java API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

Java
JavaScript

Node.js
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

C++
Java

JavaScript
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

Sharding

based on Cassandra

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

selectable replication factor

based on Cassandra

none

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

yes

Durability

Support for making data persistent

yes

in-memory journaling

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

authentication via encrypted signatures

simple password-based access control

Role-based access control

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.