DBMS > Immudb vs. Ingres vs. IRONdb vs. Snowflake vs. Trafodion

System Properties Comparison Immudb vs. Ingres vs. IRONdb vs. Snowflake vs. Trafodion

Editorial information provided by DB-Engines

Name

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

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

Description

An open source immutable (append-only) database with cryptographic verification which makes it tamper-resistant and fully auditable.

Well established RDBMS

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

Cloud-based data warehousing service for structured and semi-structured data

Transactional SQL-on-Hadoop DBMS

Primary database model

Secondary database models

Relational DBMS

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

Score	0.24
Rank	#305	Overall
	#43	Key-value stores

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

github.com/codenotary/immudb
immudb.io

www.actian.com/databases/ingres

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

www.snowflake.com

trafodion.apache.org

Technical documentation

docs.immudb.io

docs.actian.com/ingres

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

docs.snowflake.net/manuals/index.html

trafodion.apache.org/documentation.html

Developer

Codenotary

Actian Corporation

Circonus LLC.

Snowflake Computing Inc.

Apache Software Foundation, originally developed by HP

Initial release

2020

1974

originally developed at University Berkely in early 1970s

2017

2014

Current release

1.2.3, April 2022

11.2, May 2022

V0.10.20, January 2018

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C and C++

C++, Java

Server operating systems

BSD
Linux
macOS
Solaris
Windows
z/OS

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Linux

hosted

Linux

Data scheme

schema-free

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Typing

predefined data types such as float or date

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.

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

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like syntax

yes

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

yes

APIs and other access methods

gRPC protocol
PostgreSQL wire protocol

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

HTTP API

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
Python

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

JavaScript (Node.js)
Python

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

yes, in Lua

user defined functions

Java Stored Procedures

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Automatic, metric affinity per node

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Ingres Replicator

configurable replication factor, datacenter aware

yes

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

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.

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

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.