DBMS > Google Cloud Bigtable vs. HugeGraph vs. Microsoft SQL Server vs. SpaceTime vs. Yanza

System Properties Comparison Google Cloud Bigtable vs. HugeGraph vs. Microsoft SQL Server vs. SpaceTime vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

A fast-speed and highly-scalable Graph DBMS

Microsofts flagship relational DBMS

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Time Series DBMS for IoT Applications

Primary database model

Key-value store
Wide column store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Relational DBMS

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

Score	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	0.17
Rank	#335	Overall
	#31	Graph DBMS

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	0.03
Rank	#392	Overall
	#8	Spatial DBMS

Website

cloud.google.com/bigtable

github.com/hugegraph
hugegraph.apache.org

www.microsoft.com/en-us/sql-server

www.mireo.com/spacetime

yanza.com

Technical documentation

cloud.google.com/bigtable/docs

hugegraph.apache.org/docs

learn.microsoft.com/en-US/sql/sql-server

Developer

Google

Baidu

Microsoft

Mireo

Yanza

Initial release

2015

2018

1989

2020

2015

Current release

0.9

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

restricted free version is available

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

Java

C++

Server operating systems

hosted

Linux
macOS
Unix

Linux
Windows

Linux

Windows

Data scheme

schema-free

yes

schema-free

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.

yes

Secondary indexes

yes

also supports composite index and range index

yes

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

APIs and other access methods

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

Java API
RESTful HTTP API
TinkerPop Gremlin

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

RESTful HTTP API

HTTP API

Supported programming languages

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

Groovy
Java
Python

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

C#
C++
Python

any language that supports HTTP calls

Server-side scripts

Stored procedures

asynchronous Gremlin script jobs

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

depending on used storage backend, e.g. Cassandra and HBase

tables can be distributed across several files (horizontal partitioning); sharding through federation

Fixed-grid hypercubes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Internal replication in Colossus, and regional replication between two clusters in different zones

yes

depending on used storage backend, e.g. Cassandra and HBase

yes, but depending on the SQL-Server Edition

Real-time block device replication (DRBD)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via hugegraph-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

edges in graph

yes

Transaction concepts

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

Atomic single-row operations

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

User concepts

Access control

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Users, roles and permissions

fine grained access rights according to SQL-standard

yes

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.