DBMS > Heroic vs. Microsoft Azure AI Search vs. Microsoft Azure Cosmos DB vs. SWC-DB vs. Transbase

System Properties Comparison Heroic vs. Microsoft Azure AI Search vs. Microsoft Azure Cosmos DB vs. SWC-DB vs. Transbase

Editorial information provided by DB-Engines

Name

Description

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

Search-as-a-service for web and mobile app development

Globally distributed, horizontally scalable, multi-model database service

A high performance, scalable Wide Column DBMS

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Time Series DBMS

Search engine

Document store
Graph DBMS
Key-value store
Wide column store

Wide column store

Relational DBMS

Secondary database models

Vector DBMS

Spatial DBMS

Time Series DBMS

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

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	5.59
Rank	#63	Overall
	#7	Search engines

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

github.com/spotify/heroic

azure.microsoft.com/en-us/services/search

azure.microsoft.com/services/cosmos-db

github.com/kashirin-alex/swc-db
www.swcdb.org

www.transaction.de/en/products/transbase.html

Technical documentation

spotify.github.io/heroic

learn.microsoft.com/en-us/azure/search

learn.microsoft.com/azure/cosmos-db

www.transaction.de/en/products/transbase/features.html

Developer

Spotify

Microsoft

Alex Kashirin

Transaction Software GmbH

Initial release

2014

2015

2014

2020

1987

Current release

0.5, April 2021

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

GPL V3

commercial

free development license

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

C and C++

Server operating systems

hosted

Linux

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

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

RESTful HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Proprietary protocol
Thrift

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C#
Java
JavaScript
Python

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

C++

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

JavaScript

yes

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

Implicit feature of the cloud service

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

yes

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

yes

using Azure authentication

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

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.