DBMS > Faircom DB vs. Kinetica vs. SAP HANA vs. WakandaDB

System Properties Comparison Faircom DB vs. Kinetica vs. SAP HANA vs. WakandaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

Fully vectorized database across both GPUs and CPUs

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

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Object oriented 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.29
Rank	#304	Overall
	#43	Key-value stores
	#136	Relational DBMS

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.10
Rank	#356	Overall
	#17	Object oriented DBMS

Website

www.faircom.com/products/faircom-db

www.kinetica.com

www.sap.com/products/hana.html

wakanda.github.io

Technical documentation

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

docs.kinetica.com

help.sap.com/hana

wakanda.github.io/doc

Developer

FairCom Corporation

Kinetica

SAP

Wakanda SAS

Initial release

1979

2012

2010

2012

Current release

V12, November 2020

7.1, August 2021

2.0 SPS07 (April 4, 2023), April 2023

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Open Source

AGPLv3, extended commercial license available

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

ANSI C, C++

C, C++

C++, JavaScript

Server operating systems

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

Linux

Appliance or cloud-service

Linux
OS X
Windows

Data scheme

schema free, schema optional, schema required, partial schema,

yes

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

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

yes, ANSI SQL with proprietary extensions

SQL-like DML and DDL statements

yes

APIs and other access methods

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC

RESTful HTTP API

Supported programming languages

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

C++
Java
JavaScript (Node.js)
Python

JavaScript

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

user defined functions

SQLScript, R

yes

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

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

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

tunable from ACID to Eventually Consistent

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Yes, tunable from durable to delayed durability to in-memory

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 with additional protections for files

Access rights for users and roles on table level

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.