DBMS > Couchbase vs. FileMaker vs. OrigoDB vs. PostGIS

System Properties Comparison Couchbase vs. FileMaker vs. OrigoDB vs. PostGIS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

FileMaker is a cross-platform RDBMS that includes a GUI frontend.

A fully ACID in-memory object graph database

Spatial extension of PostgreSQL

Primary database model

Document store

Relational DBMS

Document store
Object oriented DBMS

Spatial DBMS

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	18.46
Rank	#36	Overall
	#5	Document stores

Score	49.73
Rank	#20	Overall
	#14	Relational DBMS

Score	0.03
Rank	#378	Overall
	#51	Document stores
	#18	Object oriented DBMS

Score	23.90
Rank	#29	Overall
	#1	Spatial DBMS

Website

www.couchbase.com

www.claris.com/filemaker

origodb.com

postgis.net

Technical documentation

docs.couchbase.com

www.claris.com/resources/documentation

origodb.com/docs

postgis.net/documentation

Developer

Couchbase, Inc.

Claris

a subsidiary of Apple

Robert Friberg et al

Initial release

2011

1983

2009

under the name LiveDB

2005

Current release

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

19.4.1, November 2021

3.4.2, February 2024

License

Commercial or Open Source

Open Source

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

commercial

Open Source

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

Server operating systems

Linux
OS X
Windows

iOS

client part only
Linux
OS X
Windows

Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

A http query request can return the data in XML format

can be achieved using .NET

yes

Secondary indexes

yes

SQL

Support of SQL

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

yes

via plugins

yes

APIs and other access methods

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

Filemaker WebDirect
JDBC
ODBC

.NET Client API
HTTP API
LINQ

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

PHP

.Net

Server-side scripts

Stored procedures

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

yes

user defined functions

Triggers

yes

via the TAP protocol

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

none

horizontal partitioning

client side managed; servers are not synchronized

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

Source-replica replication, warm standby

since Version 14

Source-replica replication

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

selectable on a per-operation basis

Immediate Consistency

Foreign keys

Referential integrity

yes

depending on model

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

Write ahead log

yes

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

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

simple rights management via user accounts and connection to external directory services

Role based authorization

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.