DBMS > jBASE vs. KeyDB vs. Microsoft Azure Cosmos DB vs. PostGIS

System Properties Comparison jBASE vs. KeyDB vs. Microsoft Azure Cosmos DB vs. PostGIS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A robust multi-value DBMS comprising development tools and middleware

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Globally distributed, horizontally scalable, multi-model database service

Spatial extension of PostgreSQL

Primary database model

Multivalue DBMS

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Spatial DBMS

Secondary database models

Spatial DBMS

Relational DBMS

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

Score	1.36
Rank	#157	Overall
	#3	Multivalue DBMS

Score	0.63
Rank	#232	Overall
	#32	Key-value stores

Score	24.97
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	20.16
Rank	#29	Overall
	#1	Spatial DBMS

Website

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

github.com/Snapchat/KeyDB
keydb.dev

azure.microsoft.com/services/cosmos-db

postgis.net

Technical documentation

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

docs.keydb.dev

learn.microsoft.com/azure/cosmos-db

postgis.net/documentation

Developer

Rocket Software (formerly Zumasys)

EQ Alpha Technology Ltd.

Microsoft

Initial release

1991

2019

2014

2005

Current release

5.7

3.4.2, February 2024

License

Commercial or Open Source

commercial

Open Source

BSD-3

commercial

Open Source

GPL v2.0

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

Server operating systems

AIX
Linux
Windows

Linux

hosted

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

optional

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

yes

JSON types

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

by using the Redis Search module

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

Embedded SQL for jBASE in BASIC

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

Proprietary protocol

RESP - REdis Serialization Protoco

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

.Net
Basic
Jabbascript
Java

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

yes

Lua

JavaScript

user defined functions

Triggers

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

yes

based on PostgreSQL

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong eventual consistency with CRDTs

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Optimistic locking, atomic execution of commands blocks and scripts

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

simple password-based access control and ACL

Access rights can be defined down to the item level

yes

based on PostgreSQL

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.