DBMS > Faircom DB vs. KeyDB vs. SAP HANA vs. Ultipa

System Properties Comparison Faircom DB vs. KeyDB vs. SAP HANA vs. Ultipa

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.

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

High performance Graph DBMS supporting HTAP high availability cluster deployment

Primary database model

Key-value store
Relational DBMS

Key-value store

Relational DBMS

Graph DBMS

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.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

Score	0.71
Rank	#226	Overall
	#33	Key-value stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.13
Rank	#335	Overall
	#31	Graph DBMS

Website

www.faircom.com/products/faircom-db

github.com/Snapchat/KeyDB
keydb.dev

www.sap.com/products/hana.html

www.ultipa.com

Technical documentation

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

docs.keydb.dev

help.sap.com/hana

www.ultipa.com/document

Developer

FairCom Corporation

EQ Alpha Technology Ltd.

SAP

Ultipa

Initial release

1979

2019

2010

2019

Current release

V12, November 2020

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

BSD-3

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

ANSI C, C++

C++

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

Data scheme

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

schema-free

yes

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

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

yes, ANSI SQL with proprietary extensions

yes

APIs and other access methods

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

Proprietary protocol

RESP - REdis Serialization Protoco

JDBC
ODBC

RESTful HTTP API

Supported programming languages

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

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

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

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

Lua

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

yes

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

Multi-source replication
Source-replica replication

yes

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

Eventual Consistency
Strong eventual consistency with CRDTs

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

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, tunable from durable to delayed durability to in-memory

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

Fine grained access rights according to SQL-standard with additional protections for files

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.