DBMS > IRONdb vs. Kinetica vs. Manticore Search vs. SQLite vs. Valentina Server

System Properties Comparison IRONdb vs. Kinetica vs. Manticore Search vs. SQLite vs. Valentina Server

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

Multi-storage database for search, including full-text search.

Widely used embeddable, in-process RDBMS

Object-relational database and reports server

Primary database model

Secondary database models

Spatial DBMS
Time Series DBMS

Time Series DBMS

using the Manticore Columnar Library

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

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	0.29
Rank	#302	Overall
	#21	Search engines

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.21
Rank	#325	Overall
	#144	Relational DBMS

Website

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

Technical documentation

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

docs.kinetica.com

manual.manticoresearch.com

www.sqlite.org/docs.html

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Circonus LLC.

Kinetica

Manticore Software

Dwayne Richard Hipp

Paradigma Software

Initial release

2017

2012

2017

2000

1999

Current release

V0.10.20, January 2018

7.1, August 2021

6.0, February 2023

3.46.0 (23 May 2024), May 2024

5.7.5

License

Commercial or Open Source

commercial

Open Source

GPL version 2

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

C++

Server operating systems

Linux

FreeBSD
Linux
macOS
Windows

server-less

Linux
OS X
Windows

Data scheme

schema-free

yes

Fixed schema

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

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

SQL-like DML and DDL statements

SQL-like query language

yes

SQL-92 is not fully supported

yes

APIs and other access methods

HTTP API

JDBC
ODBC
RESTful HTTP API

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ODBC

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

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

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

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

yes, in Lua

user defined functions

yes

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

Partitioning is done manually, search queries against distributed index is supported

none

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

Source-replica replication

Synchronous replication based on Galera library

none

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

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.