DBMS > Heroic vs. jBASE vs. Microsoft Azure Table Storage vs. SAP Advantage Database Server vs. Snowflake

System Properties Comparison Heroic vs. jBASE vs. Microsoft Azure Table Storage vs. SAP Advantage Database Server vs. Snowflake

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

A robust multi-value DBMS comprising development tools and middleware

A Wide Column Store for rapid development using massive semi-structured datasets

Low-cost RDBMS with access to ISAM and FoxPro data structures

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

Primary database model

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

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	1.49
Rank	#156	Overall
	#3	Multivalue DBMS

Score	4.04
Rank	#77	Overall
	#6	Wide column stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

github.com/spotify/heroic

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

azure.microsoft.com/en-us/services/storage/tables

www.sap.com/products/advantage-database-server.html

www.snowflake.com

Technical documentation

spotify.github.io/heroic

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

docs.snowflake.net/manuals/index.html

Developer

Spotify

Rocket Software (formerly Zumasys)

Microsoft

Sybase, SAP

Snowflake Computing Inc.

Initial release

2014

1991

2012

1993

2014

Current release

5.7

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

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

Server operating systems

AIX
Linux
Windows

hosted

Linux
Windows

hosted

Data scheme

schema-free

yes

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

Typing

predefined data types such as float or date

yes

optional

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

yes

SQL

Support of SQL

Embedded SQL for jBASE in BASIC

yes

APIs and other access methods

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

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

RESTful HTTP API

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

.Net
Basic
Jabbascript
Java

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

Delphi
Perl
PHP

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

yes

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

optimistic locking

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

caching of (temporary) tables can be configured

User concepts

Access control

Access rights can be defined down to the item level

Access rights based on private key authentication or shared access signatures

fine grained access rights according to SQL-standard

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.