DBMS > HarperDB vs. Machbase Neo vs. Oracle NoSQL vs. Snowflake

System Properties Comparison HarperDB vs. Machbase Neo vs. Oracle NoSQL vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

TimeSeries DBMS for AIoT and BigData

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Document store

Time Series DBMS

Document store
Key-value store
Relational DBMS

Relational DBMS

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

Score	0.55
Rank	#248	Overall
	#38	Document stores

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.harperdb.io

machbase.com

www.oracle.com/database/nosql/technologies/nosql

www.snowflake.com

Technical documentation

docs.harperdb.io/docs

machbase.com/dbms

docs.oracle.com/en/database/other-databases/nosql-database/index.html

docs.snowflake.net/manuals/index.html

Developer

HarperDB

Machbase

Oracle

Snowflake Computing Inc.

Initial release

2017

2013

2011

2014

Current release

3.1, August 2021

V8.0, August 2023

23.3, December 2023

License

Commercial or Open Source

commercial

free community edition available

commercial

free test version available

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

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

Node.js

Java

Server operating systems

Linux
OS X

Linux
macOS
Windows

Linux
Solaris SPARC/x86

hosted

Data scheme

dynamic schema

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

yes

JSON data types

yes

optional

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

yes

SQL

Support of SQL

SQL-like data manipulation statements

SQL-like query language

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

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

RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

C
C#
Go
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Custom Functions

since release 3.1

user defined functions

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

A table resides as a whole on one (or more) nodes in a cluster

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

the nodes on which a table resides can be defined

selectable replication factor

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

configurable

ACID within a storage node (=shard)

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes, using LMDB

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

off heap cache

User concepts

Access control

Access rights for users and roles

simple password-based access control

Access rights for users and roles

Users with fine-grained authorization concept, user roles and pluggable authentication

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.