DBMS > 4D vs. Apache IoTDB vs. GridGain vs. Oracle

System Properties Comparison 4D vs. Apache IoTDB vs. GridGain vs. Oracle

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

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

GridGain is an in-memory computing platform, built on Apache Ignite

Widely used RDBMS

Primary database model

Relational DBMS

Time Series DBMS

Key-value store
Relational DBMS

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	2.47
Rank	#110	Overall
	#54	Relational DBMS

Score	1.31
Rank	#164	Overall
	#14	Time Series DBMS

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Website

www.4d.com

iotdb.apache.org

www.gridgain.com

www.oracle.com/database

Technical documentation

developer.4d.com

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

www.gridgain.com/docs/index.html

docs.oracle.com/en/database

Developer

4D, Inc

Apache Software Foundation

GridGain Systems, Inc.

Oracle

Initial release

1984

2018

2007

1980

Current release

v20, April 2023

1.1.0, April 2023

GridGain 8.5.1

23c, September 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

restricted free version is 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

Java

Java, C++, .Net

C and C++

Server operating systems

OS X
Windows

All OS with a Java VM (>= 1.8)

Linux
OS X
Solaris
Windows

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

Data scheme

yes

Schemaless in JSON and XML columns

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

yes

close to SQL 92

SQL-like query language

ANSI-99 for query and DML statements, subset of DDL

yes

with proprietary extensions

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC
Native API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

4D proprietary IDE
PHP

C
C#
C++
Go
Java
Python
Scala

C#
C++
Java
PHP
Python
Ruby
Scala

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

Server-side scripts

Stored procedures

yes

yes (compute grid and cache interceptors can be used instead)

PL/SQL

also stored procedures in Java possible

Triggers

yes

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

none

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

Sharding

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

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

yes (replicated cache)

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes (compute grid and hadoop accelerator)

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

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

Users and groups

yes

Security Hooks for custom implementations

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.