DBMS > FatDB vs. GBase vs. Ignite vs. Splunk vs. Transbase

System Properties Comparison FatDB vs. GBase vs. Ignite vs. Splunk vs. Transbase

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.

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Analytics Platform for Big Data

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Document store
Key-value store

Relational DBMS

Key-value store
Relational DBMS

Search engine

Relational DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	1.07
Rank	#185	Overall
	#86	Relational DBMS

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

www.gbase.cn

ignite.apache.org

www.splunk.com

www.transaction.de/en/products/transbase.html

Technical documentation

apacheignite.readme.io/docs

docs.splunk.com/Documentation/Splunk

www.transaction.de/en/products/transbase/features.html

Developer

FatCloud

General Data Technology Co., Ltd.

Apache Software Foundation

Splunk Inc.

Transaction Software GmbH

Initial release

2012

2004

2015

2003

1987

Current release

GBase 8a, GBase 8s, GBase 8c

Apache Ignite 2.6

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Limited free edition and free developer edition available

commercial

free development license

Cloud-based only

Only available as a cloud 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++, Java, .Net

C and C++

Server operating systems

Windows

Linux

Linux
OS X
Solaris
Windows

FreeBSD
Linux
macOS
Solaris
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

ANSI-99 for query and DML statements, subset of DDL

Splunk Search Processing Language for search commands

yes

APIs and other access methods

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

ADO.NET
C API
JDBC
ODBC

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

HTTP REST

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

C#
Java
JavaScript
PHP
Python
Ruby

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

via applications

user defined functions

yes (compute grid and cache interceptors can be used instead)

yes

Triggers

yes

via applications

yes

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

yes (replicated cache)

Multi-source replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

yes

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

Security Hooks for custom implementations

Access rights for users and roles

fine grained access rights according to SQL-standard

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Enterprise Search Engines almost double their popularity in the last 12 months
2 July 2014, Paul Andlinger

show all

Share this page