DBMS > CouchDB vs. jBASE vs. ObjectBox vs. PostGIS vs. TempoIQ

System Properties Comparison CouchDB vs. jBASE vs. ObjectBox vs. PostGIS vs. TempoIQ

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

A robust multi-value DBMS comprising development tools and middleware

Extremely fast embedded database for small devices, IoT and Mobile

Spatial extension of PostgreSQL

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Secondary database models

Spatial DBMS

using the Geocouch extension

Time Series DBMS

Relational DBMS

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

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	1.41
Rank	#159	Overall
	#3	Multivalue DBMS

Score	1.20
Rank	#170	Overall
	#5	Object oriented DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Website

couchdb.apache.org

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

objectbox.io

postgis.net

tempoiq.com (offline)

Technical documentation

docs.couchdb.org/en/stable

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

docs.objectbox.io

postgis.net/documentation

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Rocket Software (formerly Zumasys)

ObjectBox Limited

TempoIQ

Initial release

2005

1991

2017

2005

2012

Current release

3.3.3, December 2023

5.7

3.4.2, February 2024

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Open Source

Apache License 2.0

Open Source

GPL v2.0

commercial

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

Erlang

C and C++

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

AIX
Linux
Windows

Android
iOS
Linux
macOS
Windows

Data scheme

schema-free

yes

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

via views

yes

SQL

Support of SQL

Embedded SQL for jBASE in BASIC

yes

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

Proprietary native API

HTTP API

Supported programming languages

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

.Net
Basic
Jabbascript
Java

C
C++
Dart
Go
Java
JavaScript

planned (as of Jan 2019)
Kotlin
Python

planned (as of Jan 2019)
Swift

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

View functions in JavaScript

yes

user defined functions

Triggers

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

none

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

online/offline synchronization between client and server

yes

based on PostgreSQL

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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 for users can be defined per database

Access rights can be defined down to the item level

yes

based on PostgreSQL

simple authentication-based access control

More information provided by the system vendor

News

The first On-Device Vector Database: ObjectBox 4.0
16 May 2024

Edge AI: The era of on-device AI
23 April 2024

In-Memory Database Use Cases
15 February 2024

Data Viewer for Objects – announcing ObjectBox Admin
14 November 2023

Vector Databases for Edge AI
9 August 2023

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

Couchbase climbs up the DB-Engines Ranking, increasing its popularity by 10% every month
2 June 2014, Matthias Gelbmann

show all

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

How to Automate A Blog Post App Deployment With GitHub Actions, Node.js, CouchDB, and Aptible
4 December 2023, hackernoon.com

IBM Cloudant pulls plan to fund new foundational layer for CouchDB
15 March 2022, The Register

How to install the CouchDB NoSQL database on Debian Server 11
16 June 2022, TechRepublic

CouchDB 3.0 ends admin party era • DEVCLASS
27 February 2020, DevClass

CouchDB 3.0 puts safety first
27 February 2020, InfoWorld

provided by Google News

Share this page