DBMS > Apache IoTDB vs. Graph Engine vs. Oracle vs. Valentina Server

System Properties Comparison Apache IoTDB vs. Graph Engine vs. Oracle vs. Valentina Server

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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Widely used RDBMS

Object-relational database and reports server

Primary database model

Time Series DBMS

Graph DBMS
Key-value store

Relational 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.31
Rank	#164	Overall
	#14	Time Series DBMS

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	0.21
Rank	#325	Overall
	#144	Relational DBMS

Website

iotdb.apache.org

www.graphengine.io

www.oracle.com/database

www.valentina-db.net

Technical documentation

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

www.graphengine.io/docs/manual

docs.oracle.com/en/database

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Apache Software Foundation

Microsoft

Oracle

Paradigma Software

Initial release

2018

2010

1980

1999

Current release

1.1.0, April 2023

23c, September 2023

5.7.5

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

MIT License

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

.NET and C

C and C++

Server operating systems

All OS with a Java VM (>= 1.8)

.NET

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

Linux
OS X
Windows

Data scheme

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

SQL-like query language

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
Native API

RESTful HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

ODBC

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

C#
C++
F#
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

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

yes

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)

horizontal 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

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

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Immediate 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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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'

yes

User concepts

Access control

yes

fine grained access rights according to SQL-standard

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.