DBMS > Apache Drill vs. Galaxybase vs. Machbase Neo vs. Microsoft Azure Cosmos DB

System Properties Comparison Apache Drill vs. Galaxybase vs. Machbase Neo vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Scalable, ACID-compliant native distributed parallel graph platform

TimeSeries DBMS for AIoT and BigData

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Document store
Relational DBMS

Graph DBMS

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS

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

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	0.07
Rank	#377	Overall
	#40	Graph DBMS

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

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

Website

drill.apache.org

galaxybase.com

machbase.com

azure.microsoft.com/services/cosmos-db

Technical documentation

drill.apache.org/docs

machbase.com/dbms

learn.microsoft.com/azure/cosmos-db

Developer

Apache Software Foundation

Chuanglin(Createlink) Technology Co., Ltd 浙江创邻科技有限公司

Machbase

Microsoft

Initial release

2012

2017

2013

2014

Current release

1.20.3, January 2023

Nov 20, November 2021

V8.0, August 2023

License

Commercial or Open Source

Open Source

Apache Version 2

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 and Java

Server operating systems

Linux
OS X
Windows

Linux

Linux
macOS
Windows

hosted

Data scheme

schema-free

Strong typed schema

yes

schema-free

Typing

predefined data types such as float or date

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.

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

SQL-like query language

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

Browser interface
console (shell)
Graph API (Gremlin)
OpenCypher
Proprietary native API

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

Go
Java
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

user defined functions

user defined procedures and functions

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

Relationships in graphs

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Depending on the underlying data source

yes

volatile and lookup table

User concepts

Access control

Depending on the underlying data source

Role-based access control

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.