DBMS > Badger vs. Ignite vs. ITTIA vs. Machbase Neo vs. Microsoft Azure Cosmos DB

System Properties Comparison Badger vs. Ignite vs. ITTIA vs. Machbase Neo vs. Microsoft Azure Cosmos DB

Editorial information provided by DB-Engines

Name

Description

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

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Edge Time Series DBMS with Real-Time Stream Processing

TimeSeries DBMS for AIoT and BigData

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Key-value store

Key-value store
Relational DBMS

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Relational DBMS

Spatial DBMS

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

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

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	0.39
Rank	#273	Overall
	#24	Time Series DBMS

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

github.com/dgraph-io/badger

ignite.apache.org

www.ittia.com

machbase.com

azure.microsoft.com/services/cosmos-db

Technical documentation

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

apacheignite.readme.io/docs

machbase.com/dbms

learn.microsoft.com/azure/cosmos-db

Developer

DGraph Labs

Apache Software Foundation

ITTIA L.L.C.

Machbase

Microsoft

Initial release

2017

2015

2007

2013

2014

Current release

Apache Ignite 2.6

8.7

V8.0, August 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache 2.0

commercial

free test version available

commercial

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

C++, Java, .Net

C and C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Linux
Windows

Linux
macOS
Windows

hosted

Data scheme

schema-free

yes

Fixed schema

yes

schema-free

Typing

predefined data types such as float or date

yes

Float/Blob/Integer/String/Unicode/Date/Time/Timestamp/Interval

yes

JSON types

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

yes

All properties auto-indexed by default

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

yes

SQL-like query language

APIs and other access methods

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

JDBC
ODBC
RESTful HTTP API
WebSocket

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

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

C
C++
JavaScript (Node.js)
Python

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

yes

JavaScript

Triggers

yes (cache interceptors and events)

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes (replicated cache)

yes

selectable replication factor

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

User concepts

Access control

Security Hooks for custom implementations

Database file passwords

simple password-based access control

Access rights can be defined down to the item level

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.