DBMS > Kinetica vs. Oracle NoSQL vs. OushuDB vs. SAP HANA

System Properties Comparison Kinetica vs. Oracle NoSQL vs. OushuDB vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fully vectorized database across both GPUs and CPUs

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

A data warehouse powered by Apache HAWQ supporting descriptive analysis and advanced machine learning

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

Primary database model

Relational DBMS

Document store
Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Spatial DBMS
Time Series 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.64
Rank	#236	Overall
	#109	Relational DBMS

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

Score	0.04
Rank	#363	Overall
	#154	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

www.kinetica.com

www.oracle.com/database/nosql/technologies/nosql

www.oushu.com/product/oushuDB

www.sap.com/products/hana.html

Technical documentation

docs.kinetica.com

docs.oracle.com/en/database/other-databases/nosql-database/index.html

www.oushu.com/documentation

help.sap.com/hana

Developer

Kinetica

Oracle

Oushu

SAP

Initial release

2012

2011

2010

Current release

7.1, August 2021

23.3, December 2023

4.0.1, August 2020

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

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

Java

Server operating systems

Linux

Linux
Solaris SPARC/x86

Linux

Appliance or cloud-service

Data scheme

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

Typing

predefined data types such as float or date

yes

optional

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 DML and DDL statements

Full-featured ANSI SQL support

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP API

JDBC
ODBC

Supported programming languages

C++
Java
JavaScript (Node.js)
Python

C
C#
Go
Java
JavaScript (Node.js)
Python

C
C++

Server-side scripts

Stored procedures

user defined functions

yes

SQLScript, R

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

configurable

ACID within a storage node (=shard)

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

GPU vRAM or System RAM

yes

off heap cache

yes

User concepts

Access control

Access rights for users and roles on table level

Access rights for users and roles

Kerberos, SSL and role based access

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.