DBMS > KairosDB vs. MySQL vs. Netezza vs. OrigoDB

System Properties Comparison KairosDB vs. MySQL vs. Netezza vs. OrigoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed Time Series DBMS based on Cassandra or H2

Widely used open source RDBMS

Data warehouse and analytics appliance part of IBM PureSystems

A fully ACID in-memory object graph database

Primary database model

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Document store
Object oriented DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.62
Rank	#239	Overall
	#20	Time Series DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	9.06
Rank	#46	Overall
	#29	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Website

github.com/kairosdb/kairosdb

www.mysql.com

www.ibm.com/products/netezza

origodb.com

Technical documentation

kairosdb.github.io

dev.mysql.com/doc

origodb.com/docs

Developer

Oracle

since 2010, originally MySQL AB, then Sun

IBM

Robert Friberg et al

Initial release

2013

1995

2000

2009

under the name LiveDB

Current release

1.2.2, November 2018

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C and C++

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux

included in appliance

Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

Graphite protocol
HTTP REST
Telnet API

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC
OLE DB

.NET Client API
HTTP API
LINQ

Supported programming languages

Java
JavaScript

Node.js
PHP
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C++
Fortran
Java
Lua
Perl
Python
R

.Net

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

Multi-source replication
Source-replica replication

Source-replica replication

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

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

depending on model

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

Write ahead log

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

Users with fine-grained authorization concept

no user groups or roles

Users with fine-grained authorization concept

Role based authorization

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.