DBMS > Heroic vs. Infobright vs. searchxml vs. Snowflake vs. TinkerGraph

System Properties Comparison Heroic vs. Infobright vs. searchxml vs. Snowflake vs. TinkerGraph

Editorial information provided by DB-Engines

Name

Description

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

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

DBMS for structured and unstructured content wrapped with an application server

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

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Time Series DBMS

Relational DBMS

Native XML DBMS
Search engine

Relational DBMS

Graph DBMS

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

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.13
Rank	#345	Overall
	#35	Graph DBMS

Website

github.com/spotify/heroic

ignitetech.com/softwarelibrary/infobrightdb

www.searchxml.net/category/products

www.snowflake.com

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

spotify.github.io/heroic

www.searchxml.net/support/handouts

docs.snowflake.net/manuals/index.html

Developer

Spotify

Ignite Technologies Inc.; formerly InfoBright Inc.

informationpartners gmbh

Snowflake Computing Inc.

Initial release

2014

2005

2015

2014

2009

Current release

1.0

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

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

commercial

Open Source

Apache 2.0

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

Java

C++

Java

Server operating systems

Linux
Windows

Windows

hosted

Data scheme

schema-free

yes

schema-free

yes

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

schema-free

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

yes

via Elasticsearch

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

APIs and other access methods

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET
JDBC
ODBC

RESTful HTTP API
WebDAV
XQuery
XSLT

CLI Client
JDBC
ODBC

TinkerPop 3

Supported programming languages

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

C++

most other programming languages supported via APIs

JavaScript (Node.js)
Python

Groovy
Java

Server-side scripts

Stored procedures

yes

on the application server

user defined functions

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

sychronisation to multiple collections

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

multiple readers, single writer

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional

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

Domain, group and role-based access control at the document level and for application services

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

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.