DBMS > FatDB vs. Oracle vs. Splunk vs. TerminusDB

System Properties Comparison FatDB vs. Oracle vs. Splunk vs. TerminusDB

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

Analytics Platform for Big Data

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Document store
Key-value store

Relational DBMS

Search engine

Graph DBMS

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

Document store
RDF store

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

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

www.oracle.com/database

www.splunk.com

terminusdb.com

Technical documentation

docs.oracle.com/en/database

docs.splunk.com/Documentation/Splunk

terminusdb.github.io/terminusdb/#

Developer

FatCloud

Oracle

Splunk Inc.

DataChemist Ltd.

Initial release

2012

1980

2003

2018

Current release

23c, September 2023

11.0.0, January 2023

License

Commercial or Open Source

commercial

restricted free version is available

commercial

Limited free edition and free developer edition available

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

Windows

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

Linux
OS X
Solaris
Windows

Linux

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

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

yes

with proprietary extensions

Splunk Search Processing Language for search commands

SQL-like query language (WOQL)

APIs and other access methods

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

HTTP REST

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

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
JavaScript
PHP
Python
Ruby

JavaScript
Python

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

Sharding

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

Multi-source replication

Journaling Streams

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

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

isolation level can be parameterized

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory journaling

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

Access rights for users and roles

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.