DBMS > IRONdb vs. Kinetica vs. Spark SQL vs. SQLite vs. Teradata

System Properties Comparison IRONdb vs. Kinetica vs. Spark SQL vs. SQLite vs. Teradata

Editorial information provided by DB-Engines

Name

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

Description

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

Fully vectorized database across both GPUs and CPUs

Spark SQL is a component on top of 'Spark Core' for structured data processing

Widely used embeddable, in-process RDBMS

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	45.33
Rank	#21	Overall
	#15	Relational DBMS

Website

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

Technical documentation

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

docs.kinetica.com

spark.apache.org/docs/latest/sql-programming-guide.html

www.sqlite.org/docs.html

docs.teradata.com

Developer

Circonus LLC.

Kinetica

Apache Software Foundation

Dwayne Richard Hipp

Teradata

Initial release

2017

2012

2014

2000

1984

Current release

V0.10.20, January 2018

7.1, August 2021

3.5.0 ( 2.13), September 2023

3.46.0 (23 May 2024), May 2024

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Public Domain

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++

C, C++

Scala

Server operating systems

Linux

Linux
OS X
Windows

server-less

hosted
Linux

Data scheme

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

yes

not rigid because of 'dynamic typing' concept.

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)

SQL-like DML and DDL statements

yes

SQL-92 is not fully supported

yes

SQL 2016 + extensions

APIs and other access methods

HTTP API

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

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

Supported programming languages

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

C++
Java
JavaScript (Node.js)
Python

Java
Python
R
Scala

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

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

Server-side scripts

Stored procedures

yes, in Lua

user defined functions

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic, metric affinity per node

Sharding

yes, utilizing Spark Core

none

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

Source-replica replication

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency or Eventual Consistency depending on configuration

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

via file-system locks

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

GPU vRAM or System RAM

yes

User concepts

Access control

Access rights for users and roles on table level

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.