DBMS > Galaxybase vs. Machbase Neo vs. Microsoft Azure Cosmos DB vs. OrigoDB

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

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable, ACID-compliant native distributed parallel graph platform

TimeSeries DBMS for AIoT and BigData

Globally distributed, horizontally scalable, multi-model database service

A fully ACID in-memory object graph database

Primary database model

Graph DBMS

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Document store
Object oriented DBMS

Secondary database models

Spatial DBMS

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

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

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Website

galaxybase.com

machbase.com

azure.microsoft.com/services/cosmos-db

origodb.com

Technical documentation

machbase.com/dbms

learn.microsoft.com/azure/cosmos-db

origodb.com/docs

Developer

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

Machbase

Microsoft

Robert Friberg et al

Initial release

2017

2013

2014

2009

under the name LiveDB

Current release

Nov 20, November 2021

V8.0, August 2023

License

Commercial or Open Source

commercial

free test version available

commercial

Open Source

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

Linux
macOS
Windows

hosted

Linux
Windows

Data scheme

Strong typed schema

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

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

.NET Client API
HTTP API
LINQ

Supported programming languages

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

.Net

Server-side scripts

Stored procedures

user defined procedures and functions

JavaScript

yes

Triggers

JavaScript

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Implicit feature of the cloud service

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

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

depending on model

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

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

User concepts

Access control

Role-based access control

simple password-based access control

Access rights can be defined down to the item level

Role based authorization

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.