DBMS > KairosDB vs. Oracle vs. Prometheus vs. Vitess

System Properties Comparison KairosDB vs. Oracle vs. Prometheus vs. Vitess

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 RDBMS

Open-source Time Series DBMS and monitoring system

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

Document store
Spatial DBMS

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

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	7.69
Rank	#50	Overall
	#3	Time Series DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

github.com/kairosdb/kairosdb

www.oracle.com/database

prometheus.io

vitess.io

Technical documentation

kairosdb.github.io

docs.oracle.com/en/database

prometheus.io/docs

vitess.io/docs

Developer

Oracle

The Linux Foundation, PlanetScale

Initial release

2013

1980

2015

2013

Current release

1.2.2, November 2018

23c, September 2023

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

restricted free version is available

Open Source

Apache 2.0

Open Source

Apache Version 2.0, commercial licenses available

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 and C++

Server operating systems

Linux
OS X
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Linux
Windows

Docker
Linux
macOS

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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.

yes

Import of XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

with proprietary extensions

APIs and other access methods

Graphite protocol
HTTP REST
Telnet API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

RESTful HTTP/JSON API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

Java
JavaScript

Node.js
PHP
Python

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

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

Server-side scripts

Stored procedures

PL/SQL

also stored procedures in Java possible

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding, horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

Multi-source replication
Source-replica replication

yes

by Federation

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

none

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

isolation level can be parameterized

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

User concepts

Access control

simple password-based access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or 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.