DBMS > Apache IoTDB vs. Faircom DB vs. Oracle vs. TigerGraph

System Properties Comparison Apache IoTDB vs. Faircom DB vs. Oracle vs. TigerGraph

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

Widely used RDBMS

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

Primary database model

Time Series DBMS

Key-value store
Relational DBMS

Relational DBMS

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

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

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	0.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

iotdb.apache.org

www.faircom.com/products/faircom-db

www.oracle.com/database

www.tigergraph.com

Technical documentation

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

docs.oracle.com/en/database

docs.tigergraph.com

Developer

Apache Software Foundation

FairCom Corporation

Oracle

Initial release

2018

1979

1980

2017

Current release

1.1.0, April 2023

V12, November 2020

23c, September 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Restricted, free version available

commercial

restricted free version is available

commercial

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

Java

ANSI C, C++

C and C++

C++

Server operating systems

All OS with a Java VM (>= 1.8)

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

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

Linux

Data scheme

yes

schema free, schema optional, schema required, partial schema,

yes

Schemaless in JSON and XML columns

yes

Typing

predefined data types such as float or date

yes

yes, ANSI SQL Types, JSON, typed binary structures

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

SQL-like query language

yes, ANSI SQL with proprietary extensions

yes

with proprietary extensions

SQL-like query language (GSQL)

APIs and other access methods

JDBC
Native API

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

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

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

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

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

PL/SQL

also stored procedures in Java possible

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

can be realized in PL/SQL

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

tunable from ACID to Eventually Consistent

ACID

isolation level can be parameterized

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Yes, tunable from durable to delayed durability to in-memory

yes

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

yes

Fine grained access rights according to SQL-standard with additional protections for files

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.