DBMS > Google Cloud Datastore vs. KairosDB vs. Linter vs. openGauss vs. SAP HANA

System Properties Comparison Google Cloud Datastore vs. KairosDB vs. Linter vs. openGauss vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

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

Distributed Time Series DBMS based on Cassandra or H2

RDBMS for high security requirements

An enterprise-class RDBMS compatible with high-performance, high-availability and high-performance originally developed by Huawei

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

Primary database model

Document store

Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS

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	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

Score	0.12
Rank	#350	Overall
	#152	Relational DBMS

Score	1.06
Rank	#184	Overall
	#84	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

cloud.google.com/datastore

github.com/kairosdb/kairosdb

linter.ru

gitee.com/opengauss
opengauss.org

www.sap.com/products/hana.html

Technical documentation

cloud.google.com/datastore/docs

kairosdb.github.io

docs.opengauss.org/en
gitee.com/opengauss/docs

help.sap.com/hana

Developer

Google

relex.ru

Huawei and openGauss community

SAP

Initial release

2008

2013

1990

2019

2010

Current release

1.2.2, November 2018

3.0, March 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

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

C, C++, Java

Server operating systems

hosted

Linux
OS X
Windows

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Linux

Appliance or cloud-service

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes, details here

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

SQL

Support of SQL

SQL-like query language (GQL)

yes

ANSI SQL 2011

yes

APIs and other access methods

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

Graphite protocol
HTTP REST
Telnet API

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

JDBC
ODBC

Supported programming languages

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

Java
JavaScript

Node.js
PHP
Python

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

C
C++
Java

Server-side scripts

Stored procedures

using Google App Engine

yes

proprietary syntax with the possibility to convert from PL/SQL

yes

SQLScript, R

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

none

horizontal partitioning (by range, list and hash)

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

selectable replication factor

based on Cassandra

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

based on Cassandra
Immediate Consistency

based on Cassandra

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

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

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

simple password-based access control

fine grained access rights according to SQL-standard

Access rights for users, groups and roles 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.