DBMS > Axibase vs. Couchbase vs. FatDB vs. Ingres

System Properties Comparison Axibase vs. Couchbase vs. FatDB vs. Ingres

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

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

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Well established RDBMS

Primary database model

Time Series DBMS

Document store

Document store
Key-value store

Relational 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

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

Score	0.35
Rank	#282	Overall
	#25	Time Series DBMS

Score	16.59
Rank	#36	Overall
	#5	Document stores

Score	3.80
Rank	#82	Overall
	#44	Relational DBMS

Website

axibase.com/docs/atsd/finance

www.couchbase.com

www.actian.com/databases/ingres

Technical documentation

docs.couchbase.com

docs.actian.com/ingres

Developer

Axibase Corporation

Couchbase, Inc.

FatCloud

Actian Corporation

Initial release

2013

2011

2012

1974

originally developed at University Berkely in early 1970s

Current release

15585

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

11.2, May 2022

License

Commercial or Open Source

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

Open Source

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

commercial

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

Java

C, C++, Go and Erlang

Server operating systems

Linux

Linux
OS X
Windows

Windows

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

short, integer, long, float, double, decimal, string

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.

but tools for importing/exporting data from/to XML-files available

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

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

Via inetgration in SQL Server

yes

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

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

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

Supported programming languages

Go
Java
PHP
Python
R
Ruby

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes

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

yes

via applications

yes

Triggers

yes

via the TAP protocol

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic Sharding

Sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

including cross data center replication
Source-replica replication

selectable replication factor

Ingres Replicator

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

Eventual Consistency
Immediate Consistency

Immediate 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

MVCC

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.

Can implement custom security layer via applications

fine grained access rights according to SQL-standard

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.