DBMS > AgensGraph vs. Couchbase vs. PostGIS vs. PouchDB

System Properties Comparison AgensGraph vs. Couchbase vs. PostGIS vs. PouchDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

Spatial extension of PostgreSQL

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Graph DBMS
Relational DBMS

Document store

Spatial DBMS

Document store

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector DBMS

Relational DBMS

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

Score	0.17
Rank	#320	Overall
	#29	Graph DBMS
	#143	Relational DBMS

Score	16.74
Rank	#33	Overall
	#5	Document stores

Score	20.16
Rank	#29	Overall
	#1	Spatial DBMS

Score	2.18
Rank	#114	Overall
	#21	Document stores

Website

bitnine.net/agensgraph

www.couchbase.com

postgis.net

pouchdb.com

Technical documentation

bitnine.net/documentation

docs.couchbase.com

postgis.net/documentation

pouchdb.com/guides

Developer

Bitnine Global Inc.

Couchbase, Inc.

Apache Software Foundation

Initial release

2016

2011

2005

2012

Current release

2.1, December 2018

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

3.4.2, February 2024

7.1.1, June 2019

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

Open Source

GPL v2.0

Open Source

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++, Go and Erlang

JavaScript

Server operating systems

Linux
OS X
Windows

server-less, requires a JavaScript environment (browser, Node.js)

Data scheme

depending on used data model

schema-free

yes

schema-free

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

via views

SQL

Support of SQL

yes

SQL++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

yes

APIs and other access methods

Cypher Query Language
JDBC

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

C
Java
JavaScript
Python

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

JavaScript

Server-side scripts

Stored procedures

yes

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

user defined functions

View functions in JavaScript

Triggers

yes

via the TAP protocol

yes

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

Automatic Sharding

yes

based on PostgreSQL

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

including cross data center replication
Source-replica replication

yes

based on PostgreSQL

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Ephemeral buckets

yes

User concepts

Access control

fine grained access rights according to SQL-standard

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base access control.

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.