DBMS > PostGIS vs. Postgres-XL vs. RavenDB vs. SWC-DB vs. Transbase

System Properties Comparison PostGIS vs. Postgres-XL vs. RavenDB vs. SWC-DB vs. Transbase

Editorial information provided by DB-Engines

Name

Description

Spatial extension of PostgreSQL

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Open Source Operational and Transactional Enterprise NoSQL Document Database

A high performance, scalable Wide Column DBMS

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Secondary database models

Relational DBMS

Document store
Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

Time Series DBMS

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

Score	23.90
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.52
Rank	#256	Overall
	#117	Relational DBMS

Score	3.01
Rank	#101	Overall
	#17	Document stores

Score	0.01
Rank	#387	Overall
	#13	Wide column stores

Score	0.15
Rank	#337	Overall
	#147	Relational DBMS

Website

postgis.net

www.postgres-xl.org

ravendb.net

github.com/kashirin-alex/swc-db
www.swcdb.org

www.transaction.de/en/products/transbase.html

Technical documentation

postgis.net/documentation

www.postgres-xl.org/documentation

ravendb.net/docs

www.transaction.de/en/products/transbase/features.html

Developer

Hibernating Rhinos

Alex Kashirin

Transaction Software GmbH

Initial release

2005

2014

since 2012, originally named StormDB

2010

2020

1987

Current release

3.4.2, February 2024

10 R1, October 2018

5.4, July 2022

0.5, April 2021

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

GPL v2.0

Open Source

Mozilla public license

Open Source

AGPL version 3, commercial license available

Open Source

GPL V3

commercial

free development license

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++

C and C++

Server operating systems

Linux
macOS

Linux
macOS
Raspberry Pi
Windows

Linux

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-free

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

distributed, parallel query execution

SQL-like query language (RQL)

SQL-like query language

yes

APIs and other access methods

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

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Proprietary protocol
Thrift

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

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

C++

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

based on PostgreSQL

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on PostgreSQL

Multi-source replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

MVCC

ACID, Cluster-wide transaction available

yes

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

fine grained access rights according to SQL-standard

Authorization levels configured per client per database

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.

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

RavenDB Welcomes David Baruc as Chief Revenue Officer: Seasoned Tech Leader to Drive Global Sales and ...
13 June 2023, PR Newswire

Install the NoSQL RavenDB Data System
14 May 2021, The New Stack

How I Created a RavenDB Python Client
23 September 2016, Visual Studio Magazine

RavenDB Adds Graph Queries
15 May 2019, Datanami

Review: NoSQL database RavenDB
20 March 2019, TechGenix

provided by Google News

2022 All O-Zone Football Team
17 December 2022, Ozarks Sports Zone

provided by Google News

Share this page