DBMS > Brytlyt vs. Kinetica vs. OceanBase vs. SAP HANA

System Properties Comparison Brytlyt vs. Kinetica vs. OceanBase vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable GPU-accelerated RDBMS for very fast analytic and streaming workloads, leveraging PostgreSQL

Fully vectorized database across both GPUs and CPUs

A distributed, high available RDBMS compatible with Oracle and MySQL

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

Primary database model

Relational DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

Document store
Wide column store

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	#288	Overall
	#131	Relational DBMS

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	1.66
Rank	#147	Overall
	#68	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

brytlyt.io

www.kinetica.com

en.oceanbase.com

www.sap.com/products/hana.html

Technical documentation

docs.brytlyt.io

docs.kinetica.com

en.oceanbase.com/docs/oceanbase-database

help.sap.com/hana

Developer

Brytlyt

Kinetica

OceanBase

previously Alibaba and Ant Group

SAP

Initial release

2016

2012

2010

Current release

5.0, August 2023

7.1, August 2021

4.3.0, April 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

Commercial license available

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

C, C++

C++

Server operating systems

Linux
OS X
Windows

Linux

Appliance or cloud-service

Data scheme

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

specific XML-type available, but no XML query functionality.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like DML and DDL statements

yes

APIs and other access methods

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

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Proprietary native API
Table API

JDBC
ODBC

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

C++
Java
JavaScript (Node.js)
Python

Ada

in MySQL-compatible model
C

in Oracle- and MySQL- compatible models
C++

in Oracle- and MySQL- compatible models
D

in MySQL-compatible model
Delphi

in MySQL-compatible model
Eiffel

in MySQL-compatible model
Erlang

in MySQL-compatible model
Haskell

in MySQL-compatible model
Java

in Oracle- and MySQL- compatible models
JavaScript (Node.js)

in MySQL-compatible model
Objective-C

in MySQL-compatible model
OCaml

in MySQL-compatible model
Perl

in MySQL-compatible model
PHP

in MySQL-compatible model
Python

in MySQL-compatible model
Ruby

in MySQL-compatible model
Scheme

in MySQL-compatible model
Tcl

in MySQL-compatible model

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

user defined functions

PL/SQL in oracle-compatible mode, MySQL Stored Procedure in mysql-compatible mode

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

horizontal partitioning (by hash, key, range, range columns, list, and list columns)

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication using Paxos

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles on table level

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.