DBMS > FatDB vs. GBase vs. Geode vs. Ignite

System Properties Comparison FatDB vs. GBase vs. Geode vs. Ignite

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.

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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.

Primary database model

Document store
Key-value store

Relational DBMS

Key-value store

Key-value store
Relational DBMS

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

Score	1.07
Rank	#185	Overall
	#86	Relational DBMS

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

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

Website

www.gbase.cn

geode.apache.org

ignite.apache.org

Technical documentation

geode.apache.org/docs

apacheignite.readme.io/docs

Developer

FatCloud

General Data Technology Co., Ltd.

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Apache Software Foundation

Initial release

2012

2004

2002

2015

Current release

GBase 8a, GBase 8s, GBase 8c

1.1, February 2017

Apache Ignite 2.6

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache 2.0

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

Java

C++, Java, .Net

Server operating systems

Windows

Linux

All OS with a Java VM

the JDK (8 or later) is also required

Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

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

SQL-like query language (OQL)

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

APIs and other access methods

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

ADO.NET
C API
JDBC
ODBC

Java Client API
Memcached protocol
RESTful HTTP API

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

Supported programming languages

.Net
All JVM based languages
C++
Groovy
Java
Scala

C#
C++
Java
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes

via applications

user defined functions

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

Triggers

yes

via applications

yes

Cache Event Listeners

yes (cache interceptors and events)

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

Multi-source replication

yes (replicated cache)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

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

yes, on a single node

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

Access rights per client and object definable

Security Hooks for custom implementations

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

Recent citations in the news

This is how much one of the most expensive gems costs at the Tucson gem show
11 February 2024, KGUN 9 Tucson News

Apache Geode Spawns 'All Sorts of In-Memory Things'
4 January 2017, The New Stack

Reactive Event Processing with Apache Geode
5 July 2020, InfoQ.com

1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode - Scaling Data Services with Pivotal ...
15 November 2018, O'Reilly Media

Where Does Apache Geode Fit in CQRS Architectures?
18 December 2016, InfoQ.com

provided by Google News

GridGain Announces Call for Speakers for Virtual Apache Ignite Summit 2024
8 February 2024, PR Newswire

GridGain Showcases Power of Apache Ignite at Community Over Code Conference
5 October 2023, Datanami

Apache Ignite: An Overview
6 September 2023, Open Source For You

What is Apache Ignite? How is Apache Ignite Used?
18 July 2022, The Stack

Real-time in-memory OLTP and Analytics with Apache Ignite on AWS | Amazon Web Services
14 May 2016, AWS Blog

provided by Google News

Share this page