DBMS > PostGIS vs. TempoIQ vs. Yanza

System Properties Comparison PostGIS vs. TempoIQ vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Spatial extension of PostgreSQL

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Time Series DBMS for IoT Applications

Primary database model

Spatial DBMS

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Website

postgis.net

tempoiq.com (offline)

yanza.com

Technical documentation

postgis.net/documentation

Developer

TempoIQ

Yanza

Initial release

2005

2012

2015

Current release

3.4.2, February 2024

License

Commercial or Open Source

Open Source

GPL v2.0

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Server operating systems

Windows

Data scheme

yes

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

yes

SQL

Support of SQL

yes

APIs and other access methods

HTTP API

Supported programming languages

C#
Java
JavaScript

Node.js
Python
Ruby

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Realtime Alerts

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

yes

based on PostgreSQL

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on PostgreSQL

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.

User concepts

Access control

yes

based on PostgreSQL

simple authentication-based access control

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

8 things to consider when applying for an accelerator from 2 C-level execs
29 May 2015, Built In Chicago

provided by Google News

Share this page