DBMS > FatDB vs. Oracle vs. TigerGraph vs. XTDB

System Properties Comparison FatDB vs. Oracle vs. TigerGraph vs. XTDB

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

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Document store
Key-value store

Relational DBMS

Graph DBMS

Document store

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

www.oracle.com/database

www.tigergraph.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.oracle.com/en/database

docs.tigergraph.com

www.xtdb.com/docs

Developer

FatCloud

Oracle

Juxt Ltd.

Initial release

2012

1980

2017

2019

Current release

23c, September 2023

1.19, September 2021

License

Commercial or Open Source

commercial

restricted free version is available

commercial

Open Source

MIT 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 and C++

C++

Clojure

Server operating systems

Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Linux

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

yes

with proprietary extensions

SQL-like query language (GSQL)

limited SQL, making use of Apache Calcite

APIs and other access methods

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

HTTP REST
JDBC

Supported programming languages

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

C++
Java

Clojure
Java

Server-side scripts

Stored procedures

yes

via applications

PL/SQL

also stored procedures in Java possible

yes

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding, horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can be realized in PL/SQL

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

isolation level can be parameterized

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Version 12c introduced the new option 'Oracle Database In-Memory'

User concepts

Access control

Can implement custom security layer via applications

fine grained access rights according to SQL-standard

Role-based access control

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.