DBMS > Alibaba Cloud TSDB vs. Apache Kylin vs. Google Cloud Datastore vs. KeyDB vs. SAP HANA

System Properties Comparison Alibaba Cloud TSDB vs. Apache Kylin vs. Google Cloud Datastore vs. KeyDB vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

A stable, reliable, and cost-effective online high-performance time series database service

A distributed analytics engine for big data, providing a SQL interface and multi-dimensional analysis (OLAP) and leveraging the Hadoop stack

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

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

Primary database model

Secondary database models

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.29
Rank	#301	Overall
	#26	Time Series DBMS

Score	1.25
Rank	#170	Overall
	#77	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.70
Rank	#229	Overall
	#32	Key-value stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

www.alibabacloud.com/product/hitsdb

kylin.apache.org

cloud.google.com/datastore

github.com/Snapchat/KeyDB
keydb.dev

www.sap.com/products/hana.html

Technical documentation

www.alibabacloud.com/help/en/time-series-database/latest/what-is-tsdb

kylin.apache.org/docs

cloud.google.com/datastore/docs

docs.keydb.dev

help.sap.com/hana

Developer

Alibaba

Apache Software Foundation, originally contributed from eBay Inc

Google

EQ Alpha Technology Ltd.

SAP

Initial release

2015

2008

2019

2010

Current release

3.1.0, July 2020

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Open Source

BSD-3

commercial

Cloud-based only

Only available as a cloud service

yes

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

Java

C++

Server operating systems

hosted

Linux

hosted

Linux

Appliance or cloud-service

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

Numeric data and Strings

yes

yes, details here

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

yes

SQL

Support of SQL

ANSI SQL for queries (using Apache Calcite)

SQL-like query language (GQL)

yes

APIs and other access methods

HTTP REST

JDBC
ODBC
RESTful HTTP API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

Proprietary protocol

RESP - REdis Serialization Protoco

JDBC
ODBC

Supported programming languages

Java

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

Server-side scripts

Stored procedures

using Google App Engine

Lua

SQLScript, R

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Optimistic locking, atomic execution of commands blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

Access managed on TSDB instance level

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

simple password-based access control and ACL

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.