DBMS > KairosDB vs. Kinetica vs. Oracle Berkeley DB vs. Snowflake vs. ToroDB

System Properties Comparison KairosDB vs. Kinetica vs. Oracle Berkeley DB vs. Snowflake vs. ToroDB

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Distributed Time Series DBMS based on Cassandra or H2

Fully vectorized database across both GPUs and CPUs

Widely used in-process key-value store

Cloud-based data warehousing service for structured and semi-structured data

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Time Series DBMS

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Document store

Secondary database models

Spatial DBMS
Time Series DBMS

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

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

github.com/kairosdb/kairosdb

www.kinetica.com

www.oracle.com/database/technologies/related/berkeleydb.html

www.snowflake.com

github.com/torodb/server

Technical documentation

kairosdb.github.io

docs.kinetica.com

docs.oracle.com/cd/E17076_05/html/index.html

docs.snowflake.net/manuals/index.html

Developer

Kinetica

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Snowflake Computing Inc.

8Kdata

Initial release

2013

2012

1994

2014

2016

Current release

1.2.2, November 2018

7.1, August 2021

18.1.40, May 2020

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

commercial license available

commercial

Open Source

AGPL-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, C++

C, Java, C++ (depending on the Berkeley DB edition)

Java

Server operating systems

Linux
OS X
Windows

Linux

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

hosted

All OS with a Java 7 VM

Data scheme

schema-free

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

only with the Berkeley DB XML edition

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

Graphite protocol
HTTP REST
Telnet API

JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

Java
JavaScript

Node.js
PHP
Python

C++
Java
JavaScript (Node.js)
Python

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

yes

only for the SQL API

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

Source-replica replication

yes

Source-replica replication

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

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency
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

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

GPU vRAM or System RAM

yes

User concepts

Access control

simple password-based access control

Access rights for users and roles on table level

Users with fine-grained authorization concept, user roles and pluggable authentication

Access rights for users and roles

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.