DBMS > EJDB vs. IRONdb vs. Oracle vs. Teradata

System Properties Comparison EJDB vs. IRONdb vs. Oracle vs. Teradata

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Widely used RDBMS

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Document store

Time Series 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

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	44.87
Rank	#22	Overall
	#15	Relational DBMS

Website

github.com/Softmotions/ejdb

www.circonus.com/solutions/time-series-database/

www.oracle.com/database

www.teradata.com

Technical documentation

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

docs.circonus.com/irondb/category/getting-started

docs.oracle.com/en/database

docs.teradata.com

Developer

Softmotions

Circonus LLC.

Oracle

Teradata

Initial release

2012

2017

1980

1984

Current release

V0.10.20, January 2018

23c, September 2023

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

Open Source

GPLv2

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

C and C++

Server operating systems

server-less

Linux

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

hosted
Linux

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

text, numeric, histograms

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

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

with proprietary extensions

yes

SQL 2016 + extensions

APIs and other access methods

in-process shared library

HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

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

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
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

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

yes, in Lua

PL/SQL

also stored procedures in Java possible

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Automatic, metric affinity per node

Sharding, horizontal partitioning

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

none

configurable replication factor, datacenter aware

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency per node, eventual consistency across nodes

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

isolation level can be parameterized

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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'

yes

User concepts

Access control

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.