DBMS > Couchbase vs. FileMaker vs. Heroic vs. Hive

System Properties Comparison Couchbase vs. FileMaker vs. Heroic vs. Hive

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.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

data warehouse software for querying and managing large distributed datasets, built on Hadoop

Primary database model

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

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

Score	17.30
Rank	#36	Overall
	#5	Document stores

Score	48.20
Rank	#20	Overall
	#14	Relational DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	61.17
Rank	#18	Overall
	#12	Relational DBMS

Website

www.couchbase.com

www.claris.com/filemaker

github.com/spotify/heroic

hive.apache.org

Technical documentation

docs.couchbase.com

www.claris.com/resources/documentation

spotify.github.io/heroic

cwiki.apache.org/confluence/display/Hive/Home

Developer

Couchbase, Inc.

Claris

a subsidiary of Apple

Spotify

Apache Software Foundation

initially developed by Facebook

Initial release

2011

1983

2014

2012

Current release

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

19.4.1, November 2021

3.1.3, April 2022

License

Commercial or Open Source

Open Source

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

commercial

Open Source

Apache 2.0

Open Source

Apache Version 2

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

Java

Server operating systems

Linux
OS X
Windows

iOS

client part only
Linux
OS X
Windows

All OS with a Java VM

Data scheme

schema-free

yes

schema-free

yes

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

A http query request can return the data in XML format

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

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

yes

via plugins

SQL-like DML and DDL statements

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

HQL (Heroic Query Language, a JSON-based language)
HTTP API

JDBC
ODBC
Thrift

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

PHP

C++
Java
PHP
Python

Server-side scripts

Stored procedures

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

yes

user defined functions and integration of map-reduce

Triggers

yes

via the TAP protocol

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

none

Sharding

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

yes

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Eventual Consistency
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

In-memory capabilities

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

yes

Ephemeral buckets

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

Access rights for users, groups and roles

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.