DBMS > Axibase vs. Badger vs. Couchbase vs. Microsoft Access

System Properties Comparison Axibase vs. Badger vs. Couchbase vs. Microsoft Access

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

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

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

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	0.29
Rank	#292	Overall
	#25	Time Series DBMS

Score	0.14
Rank	#331	Overall
	#49	Key-value stores

Score	17.30
Rank	#36	Overall
	#5	Document stores

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Website

axibase.com/docs/atsd/finance

github.com/dgraph-io/badger

www.couchbase.com

www.microsoft.com/en-us/microsoft-365/access

Technical documentation

godoc.org/github.com/dgraph-io/badger

docs.couchbase.com

developer.microsoft.com/en-us/access

Developer

Axibase Corporation

DGraph Labs

Couchbase, Inc.

Microsoft

Initial release

2013

2017

2011

1992

Current release

15585

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

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

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

Open Source

Apache 2.0

Open Source

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

commercial

Bundled with Microsoft Office

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

C++

Server operating systems

Linux

BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

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

yes

but not compliant to any SQL standard

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

ADO.NET
DAO
ODBC
OLE DB

Supported programming languages

Go
Java
PHP
Python
R
Ruby

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

Server-side scripts

Stored procedures

yes

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

yes

since Access 2010 using the ACE-engine

Triggers

yes

via the TAP protocol

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Automatic Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Multi-source replication

including cross data center replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

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.

a simple user-level security was built in till version Access 2003

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.