DBMS > Drizzle vs. FatDB vs. HarperDB vs. Machbase Neo

System Properties Comparison Drizzle vs. FatDB vs. HarperDB vs. Machbase Neo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

Primary database model

Relational DBMS

Document store
Key-value store

Document store

Time Series DBMS

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

Score	0.60
Rank	#244	Overall
	#38	Document stores

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Website

www.harperdb.io

machbase.com

Technical documentation

docs.harperdb.io/docs

machbase.com/dbms

Developer

Drizzle project, originally started by Brian Aker

FatCloud

HarperDB

Machbase

Initial release

2008

2012

2017

2013

Current release

7.2.4, September 2012

3.1, August 2021

V8.0, August 2023

License

Commercial or Open Source

Open Source

GNU GPL

commercial

free community edition available

commercial

free test version available

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

C++

Node.js

Server operating systems

FreeBSD
Linux
OS X

Windows

Linux
OS X

Linux
macOS
Windows

Data scheme

yes

schema-free

dynamic schema

yes

Typing

predefined data types such as float or date

yes

JSON data types

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.

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

Via inetgration in SQL Server

SQL-like data manipulation statements

SQL-like query language

APIs and other access methods

JDBC

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

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

Supported programming languages

C
C++
Java
PHP

.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

Server-side scripts

Stored procedures

yes

via applications

Custom Functions

since release 3.1

Triggers

hooks for callbacks inside the server can be used.

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor

yes

the nodes on which a table resides can be defined

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Can implement custom security layer via applications

Access rights for users and roles

simple password-based access control

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

Serent Capital invests in software firm HarperDB
12 June 2024, PE Hub

HarperDB Attracts Significant Growth Investment from Serent Capital
12 June 2024, Business Wire

HarperDB Receives Growth Investment from Serent Capital
12 June 2024, FinSMEs

Startups of the Year 2023: Meet HarperDB - A Database and Application Development Platform
22 June 2023, hackernoon.com

Jaxon Repp on HarperDB Distributed Database Platform
23 March 2022, InfoQ.com

provided by Google News

Share this page