DBMS > GeoMesa vs. Google BigQuery vs. Heroic vs. Microsoft SQL Server vs. Tibero

System Properties Comparison GeoMesa vs. Google BigQuery vs. Heroic vs. Microsoft SQL Server vs. Tibero

Editorial information provided by DB-Engines

Name

Description

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Large scale data warehouse service with append-only tables

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

Microsofts flagship relational DBMS

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	1.78
Rank	#140	Overall
	#64	Relational DBMS

Website

www.geomesa.org

cloud.google.com/bigquery

github.com/spotify/heroic

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

us.tmaxsoft.com/products/tibero

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

cloud.google.com/bigquery/docs

spotify.github.io/heroic

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

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

CCRi and others

Google

Spotify

Microsoft

TmaxSoft

Initial release

2014

2010

2014

1989

2003

Current release

4.0.5, February 2024

SQL Server 2022, November 2022

6, April 2015

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

Apache 2.0

commercial

restricted free version is 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

Scala

Java

C++

C and Assembler

Server operating systems

hosted

Linux
Windows

AIX
HP-UX
Linux
Solaris
Windows

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.

yes

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP/JSON API

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

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

user defined functions

in JavaScript

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

Persistent Stored Procedure (PSM)

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Sharding

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

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

yes, but depending on the SQL-Server Edition

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

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

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.

depending on storage layer

yes

planned for next version

User concepts

Access control

yes

depending on the DBMS used for storage

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

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.