DBMS > GeoSpock vs. Microsoft Azure SQL Database vs. Snowflake vs. TerarkDB

System Properties Comparison GeoSpock vs. Microsoft Azure SQL Database vs. Snowflake vs. TerarkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Spatial and temporal data processing engine for extreme data scale

Database as a Service offering with high compatibility to Microsoft SQL Server

Cloud-based data warehousing service for structured and semi-structured data

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Relational DBMS

Key-value store

Secondary database models

Time Series DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	78.40
Rank	#15	Overall
	#10	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Score	0.04
Rank	#377	Overall
	#58	Key-value stores

Website

geospock.com

azure.microsoft.com/en-us/products/azure-sql/database

www.snowflake.com

github.com/bytedance/terarkdb

Technical documentation

docs.microsoft.com/en-us/azure/azure-sql

docs.snowflake.net/manuals/index.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

GeoSpock

Microsoft

Snowflake Computing Inc.

ByteDance, originally Terark

Initial release

2010

2014

2016

Current release

2.0, September 2019

V12

License

Commercial or Open Source

commercial

restricted open source version available

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, Javascript

C++

Server operating systems

hosted

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

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

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC

CLI Client
JDBC
ODBC

C++ API
Java API

Supported programming languages

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

JavaScript (Node.js)
Python

C++
Java

Server-side scripts

Stored procedures

Transact SQL

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with always 3 replicas available

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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 can be defined per table

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

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.