DBMS > Axibase vs. Badger vs. MySQL vs. Postgres-XL

System Properties Comparison Axibase vs. Badger vs. MySQL vs. Postgres-XL

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.

Widely used open source RDBMS

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Primary database model

Time Series DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.21
Rank	#308	Overall
	#25	Time Series DBMS

Score	0.14
Rank	#328	Overall
	#48	Key-value stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.43
Rank	#260	Overall
	#119	Relational DBMS

Website

axibase.com/docs/atsd/finance

github.com/dgraph-io/badger

www.mysql.com

www.postgres-xl.org

Technical documentation

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

dev.mysql.com/doc

www.postgres-xl.org/documentation

Developer

Axibase Corporation

DGraph Labs

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2013

2017

1995

2014

since 2012, originally named StormDB

Current release

15585

9.0.0, July 2024

10 R1, October 2018

License

Commercial or Open Source

commercial

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

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Mozilla public license

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 and C++

Server operating systems

Linux

BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS

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.

yes

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

yes

distributed, parallel query execution

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

Go
Java
PHP
Python
R
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

yes

proprietary syntax

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

MVCC

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

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.