DBMS > Google BigQuery vs. Heroic vs. LevelDB vs. Manticore Search vs. SAP Advantage Database Server

System Properties Comparison Google BigQuery vs. Heroic vs. LevelDB vs. Manticore Search vs. SAP Advantage Database Server

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

Large scale data warehouse service with append-only tables

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

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Multi-storage database for search, including full-text search.

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

Primary database model

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	2.35
Rank	#111	Overall
	#19	Key-value stores

Score	0.22
Rank	#312	Overall
	#21	Search engines

Website

cloud.google.com/bigquery

github.com/spotify/heroic

github.com/google/leveldb

manticoresearch.com

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

Technical documentation

cloud.google.com/bigquery/docs

spotify.github.io/heroic

github.com/google/leveldb/blob/main/doc/index.md

manual.manticoresearch.com

Developer

Google

Spotify

Google

Manticore Software

Sybase, SAP

Initial release

2010

2014

2011

2017

1993

Current release

1.23, February 2021

6.0, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

BSD

Open Source

GPL version 2

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

C++

Server operating systems

hosted

Illumos
Linux
OS X
Windows

FreeBSD
Linux
macOS
Windows

Linux
Windows

Data scheme

yes

schema-free

Fixed schema

yes

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

Secondary indexes

yes

via Elasticsearch

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

RESTful HTTP/JSON API

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

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

Delphi
Perl
PHP

Server-side scripts

Stored procedures

user defined functions

in JavaScript

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

Partitioning is done manually, search queries against distributed index is supported

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Synchronous replication based on Galera library

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Since BigQuery is designed for querying data

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

yes

The original contents of fields are not stored in the Manticore index.

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

caching of (temporary) tables can be configured

User concepts

Access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.