DBMS > FatDB vs. Ingres vs. JaguarDB vs. Vitess

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

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.

Well established RDBMS

Performant, highly scalable DBMS for AI and IoT applications

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Document store
Key-value store

Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

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

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

www.actian.com/databases/ingres

www.jaguardb.com

vitess.io

Technical documentation

docs.actian.com/ingres

www.jaguardb.com/support.html

vitess.io/docs

Developer

FatCloud

Actian Corporation

DataJaguar, Inc.

The Linux Foundation, PlanetScale

Initial release

2012

1974

originally developed at University Berkely in early 1970s

2015

2013

Current release

11.2, May 2022

3.3 July 2023

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

GPL V3.0

Open Source

Apache Version 2.0, commercial licenses available

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++

the server part. Clients available in other languages

Server operating systems

Windows

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Linux

Docker
Linux
macOS

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.

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

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

with proprietary extensions

APIs and other access methods

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

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

via applications

yes

proprietary syntax

Triggers

yes

via applications

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

Ingres Replicator

Multi-source replication

Multi-source replication
Source-replica replication

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

Eventual Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

table locks or row locks depending on storage engine

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

fine grained access rights according to SQL-standard

rights management via user accounts

Users with fine-grained authorization concept

no user groups or roles

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

Vitess, the database clustering system powering YouTube, graduates CNCF incubation
5 November 2019, SiliconANGLE News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

With Vitess 4.0, database vendor matures cloud-native platform
13 November 2019, TechTarget

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

provided by Google News

Share this page