DBMS > Infobright vs. LeanXcale vs. Microsoft Azure SQL Database vs. Snowflake vs. Splunk

System Properties Comparison Infobright vs. LeanXcale vs. Microsoft Azure SQL Database vs. Snowflake vs. Splunk

Editorial information provided by DB-Engines

Name

Description

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

A highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

Database as a Service offering with high compatibility to Microsoft SQL Server

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

Analytics Platform for Big Data

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Search engine

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	0.36
Rank	#280	Overall
	#40	Key-value stores
	#129	Relational DBMS

Score	76.78
Rank	#16	Overall
	#11	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Website

ignitetech.com/softwarelibrary/infobrightdb

www.leanxcale.com

azure.microsoft.com/en-us/products/azure-sql/database

www.snowflake.com

www.splunk.com

Technical documentation

docs.microsoft.com/en-us/azure/azure-sql

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

Developer

Ignite Technologies Inc.; formerly InfoBright Inc.

LeanXcale

Microsoft

Snowflake Computing Inc.

Splunk Inc.

Initial release

2005

2015

2010

2014

2003

Current release

V12

License

Commercial or Open Source

commercial

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

commercial

Limited free edition and free developer edition available

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

Server operating systems

Linux
Windows

hosted

Linux
OS X
Solaris
Windows

Data scheme

yes

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

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

Secondary indexes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

through Apache Derby

yes

Splunk Search Processing Language for search commands

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

ADO.NET
JDBC
ODBC

CLI Client
JDBC
ODBC

HTTP REST

Supported programming languages

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

C
Java
Scala

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

Transact SQL

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes, with always 3 replicas available

yes

Multi-source 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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

Concurrency

Support for concurrent manipulation of data

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

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

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

Access rights for users and 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.