DBMS > Google BigQuery vs. Microsoft Azure Synapse Analytics vs. Microsoft Azure Table Storage vs. Sphinx vs. TigerGraph

System Properties Comparison Google BigQuery vs. Microsoft Azure Synapse Analytics vs. Microsoft Azure Table Storage vs. Sphinx vs. TigerGraph

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

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

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

Open source search engine for searching in data from different sources, e.g. relational databases

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	20.56
Rank	#31	Overall
	#19	Relational DBMS

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

cloud.google.com/bigquery

azure.microsoft.com/services/synapse-analytics

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

sphinxsearch.com

www.tigergraph.com

Technical documentation

cloud.google.com/bigquery/docs

docs.microsoft.com/azure/synapse-analytics

sphinxsearch.com/docs

docs.tigergraph.com

Developer

Google

Microsoft

Sphinx Technologies Inc.

Initial release

2010

2016

2012

2001

2017

Current release

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2, commercial licence available

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

C++

Server operating systems

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux

Data scheme

yes

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

full-text index on all search fields

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

SQL-like query language (GSQL)

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

RESTful HTTP API

Proprietary protocol

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
Java
PHP

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

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C++
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Transact SQL

yes

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding, horizontal partitioning

Sharding

Implicit feature of the cloud service

Sharding

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

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.

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

yes

Relationships in graphs

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

optimistic locking

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 Sphinx index.

yes

In-memory capabilities

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

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

yes

Access rights based on private key authentication or shared access signatures

Role-based access control

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.