DBMS > Amazon Redshift vs. Axibase vs. Badger vs. Machbase Neo vs. MarkLogic

System Properties Comparison Amazon Redshift vs. Axibase vs. Badger vs. Machbase Neo vs. MarkLogic

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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.

TimeSeries DBMS for AIoT and BigData

Operational and transactional Enterprise NoSQL database

Primary database model

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.35
Rank	#282	Overall
	#25	Time Series DBMS

Score	0.22
Rank	#320	Overall
	#47	Key-value stores

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	5.18
Rank	#63	Overall
	#11	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#7	Search engines

Website

aws.amazon.com/redshift

axibase.com/docs/atsd/finance

github.com/dgraph-io/badger

machbase.com

www.marklogic.com

Technical documentation

docs.aws.amazon.com/redshift

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

machbase.com/dbms

docs.marklogic.com

Developer

Amazon (based on PostgreSQL)

Axibase Corporation

DGraph Labs

Machbase

MarkLogic Corp.

Initial release

2012

2013

2017

2013

2001

Current release

15585

V8.0, August 2023

11.0, December 2022

License

Commercial or Open Source

commercial

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

Open Source

Apache 2.0

commercial

free test version available

commercial

restricted free version is available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++

Server operating systems

hosted

Linux

BSD
Linux
OS X
Solaris
Windows

Linux
macOS
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

schema-free

Schema can be enforced

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.

yes

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

yes

SQL92

APIs and other access methods

JDBC
ODBC

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

Supported programming languages

All languages supporting JDBC/ODBC

Go
Java
PHP
Python
R
Ruby

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

C
C#
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

yes

via XQuery or JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

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

ACID

can act as a resource manager in an XA/JTA transaction

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

volatile and lookup table

yes, with Range Indexes

User concepts

Access control

fine grained access rights according to SQL-standard

simple password-based access control

Role-based access control at the document and subdocument levels

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.