DBMS > GeoMesa vs. Google BigQuery vs. Quasardb vs. TimescaleDB vs. Valentina Server

System Properties Comparison GeoMesa vs. Google BigQuery vs. Quasardb vs. TimescaleDB vs. Valentina Server

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

Distributed, high-performance timeseries database

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Object-relational database and reports server

Primary database model

Secondary database models

Relational DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Score	0.21
Rank	#325	Overall
	#144	Relational DBMS

Website

www.geomesa.org

cloud.google.com/bigquery

quasar.ai

www.timescale.com

www.valentina-db.net

Technical documentation

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

cloud.google.com/bigquery/docs

doc.quasar.ai/master

docs.timescale.com

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

CCRi and others

Google

quasardb

Timescale

Paradigma Software

Initial release

2014

2010

2009

2017

1999

Current release

5.0.0, May 2024

3.14.1, January 2024

2.15.0, May 2024

5.7.5

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

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

Open Source

Apache 2.0

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

C++

Server operating systems

hosted

BSD
Linux
OS X
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

integer and binary

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

with tags

yes

SQL

Support of SQL

yes

SQL-like query language

yes

full PostgreSQL SQL syntax

yes

APIs and other access methods

RESTful HTTP/JSON API

HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

ODBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

user defined functions

in JavaScript

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Sharding

consistent hashing

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Source-replica replication with selectable replication factor

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

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

by using LevelDB

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

Transient mode

yes

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)

Cryptographically strong user authentication and audit trail

fine grained access rights according to SQL-standard

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.