DBMS > FatDB vs. GBase vs. SAP HANA vs. WakandaDB

System Properties Comparison FatDB vs. GBase vs. SAP HANA vs. WakandaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

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

Document store
Key-value store

Relational DBMS

Object oriented 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	1.07
Rank	#185	Overall
	#86	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

www.gbase.cn

www.sap.com/products/hana.html

wakanda.github.io

Technical documentation

help.sap.com/hana

wakanda.github.io/doc

Developer

FatCloud

General Data Technology Co., Ltd.

SAP

Wakanda SAS

Initial release

2012

2004

2010

2012

Current release

GBase 8a, GBase 8s, GBase 8c

2.0 SPS07 (April 4, 2023), April 2023

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

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

C, Java, Python

C++, JavaScript

Server operating systems

Windows

Linux

Appliance or cloud-service

Linux
OS X
Windows

Data scheme

schema-free

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

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

Standard with numerous extensions

yes

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

ADO.NET
C API
JDBC
ODBC

JDBC
ODBC

RESTful HTTP API

Supported programming languages

JavaScript

Server-side scripts

Stored procedures

yes

via applications

user defined functions

SQLScript, R

yes

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by range, list and hash) and vertical partitioning

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

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

User concepts

Access control

Can implement custom security layer via applications

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.