DBMS > EventStoreDB vs. gStore vs. Heroic vs. OushuDB

System Properties Comparison EventStoreDB vs. gStore vs. Heroic vs. OushuDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Industrial-strength, open-source database solution built from the ground up for event sourcing.

A native Graph DBMS to store and maintain very large RDF datasets.

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

A data warehouse powered by Apache HAWQ supporting descriptive analysis and advanced machine learning

Primary database model

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

Score	1.19
Rank	#173	Overall
	#1	Event Stores

Score	0.14
Rank	#342	Overall
	#34	Graph DBMS
	#16	RDF stores

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	0.10
Rank	#355	Overall
	#154	Relational DBMS

Website

www.eventstore.com

en.gstore.cn

github.com/spotify/heroic

www.oushu.com/product/oushuDB

Technical documentation

developers.eventstore.com

en.gstore.cn/#/enDocs

spotify.github.io/heroic

www.oushu.com/documentation

Developer

Event Store Limited

Spotify

Oushu

Initial release

2012

2016

2014

Current release

21.2, February 2021

1.2, November 2023

4.0.1, August 2020

License

Commercial or Open Source

Open Source

BSD

Open Source

Apache 2.0

commercial

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

Java

Server operating systems

Linux
Windows

Linux

Data scheme

schema-free and OWL/RDFS-schema support

schema-free

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.

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

Full-featured ANSI SQL support

APIs and other access methods

HTTP API
SPARQL 1.1

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

JDBC
ODBC

Supported programming languages

C++
Java
JavaScript (Node.js)
PHP
Python

C
C++

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

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.

User concepts

Access control

Users, roles and permissions, Role-Based Access Control (RBAC) supported

Kerberos, SSL and role based access

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

China's answer to Snowflake is shaping as data demands upgrade
8 September 2021, PingWest

provided by Google News

Share this page