DBMS > FatDB vs. Ignite vs. Ingres vs. JaguarDB

System Properties Comparison FatDB vs. Ignite vs. Ingres vs. JaguarDB

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.

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.

Well established RDBMS

Performant, highly scalable DBMS for AI and IoT applications

Primary database model

Document store
Key-value store

Key-value store
Relational DBMS

Relational DBMS

Key-value store
Vector DBMS

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

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

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Website

ignite.apache.org

www.actian.com/databases/ingres

www.jaguardb.com

Technical documentation

apacheignite.readme.io/docs

docs.actian.com/ingres

www.jaguardb.com/support.html

Developer

FatCloud

Apache Software Foundation

Actian Corporation

DataJaguar, Inc.

Initial release

2012

2015

1974

originally developed at University Berkely in early 1970s

2015

Current release

Apache Ignite 2.6

11.2, May 2022

3.3 July 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

GPL V3.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, .Net

C++

the server part. Clients available in other languages

Server operating systems

Windows

Linux
OS X
Solaris
Windows

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Linux

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

but tools for importing/exporting data from/to XML-files available

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

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

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

APIs and other access methods

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

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

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

JDBC
ODBC

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes

via applications

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

yes

Triggers

yes

via applications

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes (replicated cache)

Ingres Replicator

Multi-source replication

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

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

MVCC

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

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

rights management via user accounts

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

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

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

GridGain Releases Conference Schedule for Virtual Apache Ignite Summit 2023
1 June 2023, Datanami

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

Postgres pioneer Michael Stonebraker promises to upend the database once more
26 December 2023, The Register

New startup from Postgres creator puts the database at heart of software stack
12 March 2024, TechCrunch

Actian Launches Ingres as a Fully-Managed Cloud Service
24 September 2021, Integration Developers

PostgreSQL now top developer choice ahead of MySQL, according to massive new survey • DEVCLASS
13 June 2023, DevClass

Dr. Michael Stonebraker: A Short History of Database Systems
1 February 2019, The New Stack

provided by Google News

Share this page