DBMS > GeoSpock vs. Microsoft Azure SQL Database vs. Quasardb vs. SQLite vs. TimescaleDB

System Properties Comparison GeoSpock vs. Microsoft Azure SQL Database vs. Quasardb vs. SQLite vs. TimescaleDB

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

Distributed, high-performance timeseries database

Widely used embeddable, in-process RDBMS

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

Primary database model

Secondary database models

Time Series DBMS

Document store
Graph DBMS
Spatial DBMS

Relational DBMS

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

Score	76.78
Rank	#16	Overall
	#11	Relational DBMS

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

geospock.com

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

quasar.ai

www.sqlite.org

www.timescale.com

Technical documentation

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

doc.quasar.ai/master

www.sqlite.org/docs.html

docs.timescale.com

Developer

GeoSpock

Microsoft

quasardb

Dwayne Richard Hipp

Timescale

Initial release

2010

2009

2000

2017

Current release

2.0, September 2019

V12

3.14.1, January 2024

3.46.0 (23 May 2024), May 2024

2.15.0, May 2024

License

Commercial or Open Source

commercial

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

Open Source

Public Domain

Open Source

Apache 2.0

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

BSD
Linux
OS X
Windows

server-less

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

integer and binary

yes

not rigid because of 'dynamic typing' concept.

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

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

with tags

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

SQL-like query language

yes

SQL-92 is not fully supported

yes

full PostgreSQL SQL syntax

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC

HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

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

Supported programming languages

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

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

Transact SQL

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

consistent hashing

none

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with always 3 replicas available

Source-replica replication with selectable replication factor

none

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

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

via file-system locks

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.

yes

Transient mode

yes

User concepts

Access control

Access rights for users can be defined per table

fine grained access rights according to SQL-standard

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.