DBMS > Google BigQuery vs. Manticore Search vs. Microsoft Azure Synapse Analytics vs. Quasardb

System Properties Comparison Google BigQuery vs. Manticore Search vs. Microsoft Azure Synapse Analytics vs. Quasardb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

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

Elastic, large scale data warehouse service leveraging the broad eco-system of SQL Server

Distributed, high-performance timeseries database

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	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.29
Rank	#302	Overall
	#21	Search engines

Score	19.93
Rank	#31	Overall
	#19	Relational DBMS

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Website

cloud.google.com/bigquery

manticoresearch.com

azure.microsoft.com/services/synapse-analytics

quasar.ai

Technical documentation

cloud.google.com/bigquery/docs

manual.manticoresearch.com

docs.microsoft.com/azure/synapse-analytics

doc.quasar.ai/master

Developer

Google

Manticore Software

Microsoft

quasardb

Initial release

2010

2017

2016

2009

Current release

6.0, February 2023

3.14.1, January 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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

C++

Server operating systems

hosted

FreeBSD
Linux
macOS
Windows

hosted

BSD
Linux
OS X
Windows

Data scheme

yes

Fixed schema

yes

schema-free

Typing

predefined data types such as float or date

yes

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

yes

integer and binary

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

full-text index on all search fields

yes

with tags

SQL

Support of SQL

yes

SQL-like query language

yes

SQL-like query language

APIs and other access methods

RESTful HTTP/JSON API

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

ADO.NET
JDBC
ODBC

HTTP API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

C#
Java
PHP

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

user defined functions

Transact SQL

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

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

Sharding, horizontal partitioning

Sharding

consistent hashing

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication based on Galera library

yes

Source-replica replication with selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints

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

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

yes

by using LevelDB

In-memory capabilities

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

yes

Transient mode

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

yes

Cryptographically strong user authentication and audit trail

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.