DBMS > jBASE vs. PostGIS vs. Snowflake vs. Transbase vs. YDB

System Properties Comparison jBASE vs. PostGIS vs. Snowflake vs. Transbase vs. YDB

Editorial information provided by DB-Engines

Name

Description

A robust multi-value DBMS comprising development tools and middleware

Spatial extension of PostgreSQL

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

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

A distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

Primary database model

Multivalue DBMS

Spatial DBMS

Relational DBMS

Document store
Relational DBMS

Secondary database models

Relational DBMS

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

Score	1.41
Rank	#159	Overall
	#3	Multivalue DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Score	0.35
Rank	#278	Overall
	#43	Document stores
	#127	Relational DBMS

Website

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

postgis.net

www.snowflake.com

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

github.com/ydb-platform/ydb
ydb.tech

Technical documentation

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

postgis.net/documentation

docs.snowflake.net/manuals/index.html

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

ydb.tech/en/docs

Developer

Rocket Software (formerly Zumasys)

Snowflake Computing Inc.

Transaction Software GmbH

Yandex

Initial release

1991

2005

2014

1987

2019

Current release

5.7

3.4.2, February 2024

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

GPL v2.0

commercial

free development license

Open Source

Apache 2.0; commercial license available

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

Server operating systems

AIX
Linux
Windows

hosted

FreeBSD
Linux
macOS
Solaris
Windows

Linux

Data scheme

schema-free

yes

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

yes

Flexible Schema (defined schema, partial schema, schema free)

Typing

predefined data types such as float or date

optional

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

Embedded SQL for jBASE in BASIC

yes

SQL-like query language (YQL)

APIs and other access methods

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP API (DynamoDB compatible)

Supported programming languages

.Net
Basic
Jabbascript
Java

JavaScript (Node.js)
Python

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

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

yes

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

based on PostgreSQL

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on PostgreSQL

yes

Source-replica replication

Active-passive shard replication

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

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

Access rights can be defined down to the item level

yes

based on PostgreSQL

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

fine grained access rights according to SQL-standard

Access rights defined for Yandex Cloud users

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.