DBMS > Infobright vs. Postgres-XL vs. Splunk vs. Vitess

System Properties Comparison Infobright vs. Postgres-XL vs. Splunk vs. Vitess

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

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Analytics Platform for Big Data

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

Search engine

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.88
Rank	#198	Overall
	#92	Relational DBMS

Score	0.43
Rank	#260	Overall
	#119	Relational DBMS

Score	93.02
Rank	#13	Overall
	#2	Search engines

Score	0.86
Rank	#202	Overall
	#95	Relational DBMS

Website

ignitetech.com/softwarelibrary/infobrightdb

www.postgres-xl.org

www.splunk.com

vitess.io

Technical documentation

www.postgres-xl.org/documentation

docs.splunk.com/Documentation/Splunk

vitess.io/docs

Developer

Ignite Technologies Inc.; formerly InfoBright Inc.

Splunk Inc.

The Linux Foundation, PlanetScale

Initial release

2005

2014

since 2012, originally named StormDB

2003

2013

Current release

10 R1, October 2018

15.0.2, December 2022

License

Commercial or Open Source

commercial

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

Open Source

Mozilla public license

commercial

Limited free edition and free developer edition available

Open Source

Apache Version 2.0, commercial licenses available

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

Server operating systems

Linux
Windows

Linux
macOS

Linux
OS X
Solaris
Windows

Docker
Linux
macOS

Data scheme

yes

Typing

predefined data types such as float or date

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

XML type, but no XML query functionality

yes

Secondary indexes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

distributed, parallel query execution

Splunk Search Processing Language for search commands

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

HTTP REST

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

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

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C#
Java
JavaScript
PHP
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

Multi-source replication
Source-replica replication

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

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

MVCC

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

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

Access rights for users and roles

Users with fine-grained authorization concept

no user groups or roles

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

DB-Engines blog posts

Enterprise Search Engines almost double their popularity in the last 12 months
2 July 2014, Paul Andlinger

show all

Recent citations in the news

Deepthi Sigireddi on Distributed Database Architecture in the Cloud Native Era
20 May 2024, InfoQ.com

They scaled YouTube — now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale offers undo button to reverse schema migration without losing data
24 March 2022, The Register

CNCF’s Vitess Scales MySQL with the Help of Kubernetes
9 February 2018, The New Stack

provided by Google News

Share this page