DBMS > PostGIS vs. RocksDB vs. SAP Adaptive Server vs. Trafodion

System Properties Comparison PostGIS vs. RocksDB vs. SAP Adaptive Server vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

Spatial extension of PostgreSQL

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

The SAP (Sybase) Adaptive Server Enterprise (ASE) is an enterprise-class RDBMS

Transactional SQL-on-Hadoop DBMS

Primary database model

Spatial DBMS

Key-value store

Relational DBMS

Secondary database models

Relational DBMS

Spatial DBMS

with Boeing's Spatial Query Server

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

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	36.31
Rank	#25	Overall
	#17	Relational DBMS

Website

postgis.net

rocksdb.org

www.sap.com/products/technology-platform/sybase-ase.html

trafodion.apache.org

Technical documentation

postgis.net/documentation

github.com/facebook/rocksdb/wiki

help.sap.com/docs/SAP_ASE

trafodion.apache.org/documentation.html

Developer

Facebook, Inc.

SAP, Sybase

Apache Software Foundation, originally developed by HP

Initial release

2005

2013

1987

2014

Current release

3.4.2, February 2024

8.11.4, April 2024

16.0

2.3.0, February 2019

License

Commercial or Open Source

Open Source

GPL v2.0

Open Source

BSD

commercial

Open Source

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

C and C++

C++, Java

Server operating systems

Linux

AIX
HP-UX
Linux
Solaris
Unix
Windows

Linux

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

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

C++ API
Java API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

ADO.NET
JDBC
ODBC

Supported programming languages

C
C++
Go
Java
Perl
Python
Ruby

C
C++
Cobol
Java
Java
Perl
PHP
Python

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

user defined functions

Java and Transact-SQL

Java Stored Procedures

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

yes

Multi-source replication
Source-replica replication

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

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

yes

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

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.