DBMS > Infobright vs. Linter vs. Riak KV vs. XTDB

System Properties Comparison Infobright vs. Linter vs. Riak KV vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

RDBMS for high security requirements

Distributed, fault tolerant key-value store

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Document store

Secondary database models

Spatial DBMS

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

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

ignitetech.com/softwarelibrary/infobrightdb

linter.ru

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

www.tiot.jp/riak-docs/riak/kv/latest

www.xtdb.com/docs

Developer

Ignite Technologies Inc.; formerly InfoBright Inc.

relex.ru

OpenSource, formerly Basho Technologies

Juxt Ltd.

Initial release

2005

1990

2009

2019

Current release

3.2.0, December 2022

1.19, September 2021

License

Commercial or Open Source

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

commercial

Open Source

Apache version 2, commercial enterprise edition

Open Source

MIT License

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

Erlang

Clojure

Server operating systems

Linux
Windows

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Linux
OS X

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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.

Secondary indexes

Knowledge Grid Technology used instead

yes

restricted

yes

SQL

Support of SQL

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

HTTP API
Native Erlang Interface

HTTP REST
JDBC

Supported programming languages

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Clojure
Java

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

fine grained access rights according to SQL-standard

yes, using Riak Security

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

СУБД «Линтер Бастион» прошла сертификацию ФСТЭК России по новым требованиям к системам управления ...
11 March 2024, ServerNews

provided by Google News

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

A Critique of Resizable Hash Tables: Riak Core & Random Slicing
26 August 2018, InfoQ.com

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

NoSQL pioneer Basho stamps its mark on time stamp data with Riak TS
6 October 2015, The Register

provided by Google News

Share this page