DBMS > EsgynDB vs. KairosDB vs. Postgres-XL vs. SAP HANA

System Properties Comparison EsgynDB vs. KairosDB vs. Postgres-XL vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Distributed Time Series DBMS based on Cassandra or H2

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

www.esgyn.cn

github.com/kairosdb/kairosdb

www.postgres-xl.org

www.sap.com/products/hana.html

Technical documentation

kairosdb.github.io

www.postgres-xl.org/documentation

help.sap.com/hana

Developer

Esgyn

SAP

Initial release

2015

2013

2014

since 2012, originally named StormDB

2010

Current release

1.2.2, November 2018

10 R1, October 2018

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Mozilla public license

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++, Java

Java

Server operating systems

Linux

Linux
OS X
Windows

Linux
macOS

Appliance or cloud-service

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

distributed, parallel query execution

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

Graphite protocol
HTTP REST
Telnet API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

Java
JavaScript

Node.js
PHP
Python

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

horizontal partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

selectable replication factor

based on Cassandra

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

MVCC

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

User concepts

Access control

fine grained access rights according to SQL-standard

simple password-based access control

fine grained access rights according to SQL-standard

yes

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.