DBMS > PostGIS vs. YTsaurus

System Properties Comparison PostGIS vs. YTsaurus

Please select another system to include it in the comparison.

Our visitors often compare PostGIS and YTsaurus with MongoDB, Databricks and OpenSearch.

Editorial information provided by DB-Engines

Name

Description

Spatial extension of PostgreSQL

YTsaurus is an open source platform for distributed storage and processing.

Primary database model

Spatial DBMS

Document store
Key-value store

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

Score	0.11
Rank	#340	Overall
	#45	Document stores
	#50	Key-value stores

Website

postgis.net

ytsaurus.tech

Technical documentation

postgis.net/documentation

ytsaurus.tech/docs/en

Developer

Yandex

Initial release

2005

2023

Current release

3.4.2, February 2024

License

Commercial or Open Source

Open Source

GPL v2.0

Open Source

Apache License, Version 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

Server operating systems

Ubuntu

Data scheme

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

SQL

Support of SQL

yes

YQL, an SQL-based language, is supported

Supported programming languages

C++
Go
Java
JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

based on PostgreSQL

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on PostgreSQL

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

Access Control Lists

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.