DBMS > Apache IoTDB vs. EJDB vs. Ingres vs. Trafodion

System Properties Comparison Apache IoTDB vs. EJDB vs. Ingres vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Well established RDBMS

Transactional SQL-on-Hadoop DBMS

Primary database model

Time Series DBMS

Document store

Relational DBMS

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

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

Website

iotdb.apache.org

github.com/Softmotions/ejdb

www.actian.com/databases/ingres

trafodion.apache.org

Technical documentation

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

github.com/Softmotions/ejdb/blob/master/README.md

docs.actian.com/ingres

trafodion.apache.org/documentation.html

Developer

Apache Software Foundation

Softmotions

Actian Corporation

Apache Software Foundation, originally developed by HP

Initial release

2018

2012

1974

originally developed at University Berkely in early 1970s

2014

Current release

1.1.0, April 2023

11.2, May 2022

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GPLv2

commercial

Open Source

Apache 2.0

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

C++, Java

Server operating systems

All OS with a Java VM (>= 1.8)

server-less

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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.

but tools for importing/exporting data from/to XML-files available

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

JDBC
Native API

in-process shared library

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

ADO.NET
JDBC
ODBC

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

none

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding

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

none

Ingres Replicator

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

MVCC

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

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

TsFile: A Standard Format for IoT Time Series Data
27 February 2024, The New Stack

Linux 6.5 With AMD P-State EPP Default Brings Performance & Power Efficiency Benefits For Ryzen Servers
21 September 2023, Phoronix

AMD EPYC 8324P / 8324PN Siena 32-Core Siena Linux Server Performance Review
10 October 2023, Phoronix

Apache Promotes IoT Database Project
25 September 2020, Datanami

Timecho Raises Over US$10M in First Funding
29 June 2022, FinSMEs

provided by Google News

Ingres CEO Burkhardt will bring open source perspective to Cloud Panel
10 May 2024, Database Journal

Postgres pioneer Michael Stonebraker promises to upend the database once more
26 December 2023, The Register

New startup from Postgres creator puts the database at heart of software stack
12 March 2024, TechCrunch

Actian Launches Ingres as a Fully-Managed Cloud Service
24 September 2021, Integration Developers

PostgreSQL now top developer choice ahead of MySQL, according to massive new survey • DEVCLASS
13 June 2023, DevClass

provided by Google News

Low-latency, distributed database architectures are critical for emerging fog applications
7 April 2022, Embedded Computing Design

provided by Google News

Share this page