DBMS > PostGIS vs. Sequoiadb vs. Snowflake vs. TimescaleDB vs. VelocityDB

System Properties Comparison PostGIS vs. Sequoiadb vs. Snowflake vs. TimescaleDB vs. VelocityDB

Editorial information provided by DB-Engines

Name

Description

Spatial extension of PostgreSQL

NewSQL database with distributed OLTP and SQL

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

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

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Spatial DBMS

Document store
Relational DBMS

Relational DBMS

Time Series DBMS

Graph DBMS
Object oriented DBMS

Secondary database models

Relational DBMS

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

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.50
Rank	#258	Overall
	#41	Document stores
	#120	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Score	0.11
Rank	#354	Overall
	#37	Graph DBMS
	#15	Object oriented DBMS

Website

Technical documentation

postgis.net/documentation

www.sequoiadb.com/en/index.php?m=Files&a=index

docs.snowflake.net/manuals/index.html

docs.timescale.com

velocitydb.com/UserGuide

Developer

Sequoiadb Ltd.

Snowflake Computing Inc.

Timescale

VelocityDB Inc

Initial release

2005

2013

2014

2017

2011

Current release

3.4.2, February 2024

2.15.0, May 2024

7.x

License

Commercial or Open Source

Open Source

GPL v2.0

Open Source

Server: AGPL; Client: Apache V2

commercial

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

C++

Server operating systems

Linux

hosted

Linux
OS X
Windows

Any that supports .NET

Data scheme

yes

schema-free

yes

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

yes

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

yes

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

SQL

Support of SQL

yes

SQL-like query language

yes

full PostgreSQL SQL syntax

APIs and other access methods

proprietary protocol using JSON

CLI Client
JDBC
ODBC

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

.Net

Supported programming languages

.Net
C++
Java
PHP
Python

JavaScript (Node.js)
Python

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

.Net

Server-side scripts

Stored procedures

user defined functions

JavaScript

user defined functions

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

similar concept for controling cloud resources

yes

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

yes

based on PostgreSQL

Sharding

yes

yes, across time and space (hash partitioning) attributes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on PostgreSQL

Source-replica replication

yes

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Document is locked during a transaction

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

yes

based on PostgreSQL

simple password-based access control

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

fine grained access rights according to SQL-standard

Based on Windows 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.