DBMS > Heroic vs. searchxml vs. Stardog vs. Tkrzw

System Properties Comparison Heroic vs. searchxml vs. Stardog vs. Tkrzw

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

DBMS for structured and unstructured content wrapped with an application server

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Time Series DBMS

Native XML DBMS
Search engine

Graph DBMS
RDF store

Key-value store

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

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

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

Score	2.07
Rank	#122	Overall
	#11	Graph DBMS
	#6	RDF stores

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

github.com/spotify/heroic

www.searchxml.net/category/products

www.stardog.com

dbmx.net/tkrzw

Technical documentation

spotify.github.io/heroic

www.searchxml.net/support/handouts

docs.stardog.com

Developer

Spotify

informationpartners gmbh

Stardog-Union

Mikio Hirabayashi

Initial release

2014

2015

2010

2020

Current release

1.0

7.3.0, May 2020

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

Open Source

Apache Version 2.0

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

Java

C++

Java

C++

Server operating systems

Windows

Linux
macOS
Windows

Linux
macOS

Data scheme

schema-free

schema-free and OWL/RDFS-schema support

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

Import/export of XML data possible

Secondary indexes

yes

via Elasticsearch

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

APIs and other access methods

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

RESTful HTTP API
WebDAV
XQuery
XSLT

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

Supported programming languages

C++

most other programming languages supported via APIs

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

on the application server

user defined functions and aggregates, HTTP Server extensions in Java

Triggers

yes

via event handlers

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

sychronisation to multiple collections

Multi-source replication in HA-Cluster

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

Immediate Consistency in HA-Cluster

Immediate Consistency

Foreign keys

Referential integrity

yes

relationships in graphs

Transaction concepts

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

multiple readers, single writer

ACID

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

using specific database classes

User concepts

Access control

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

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.

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

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

provided by Google News

Share this page