DBMS > Drizzle vs. EDB Postgres vs. FatDB vs. Machbase Neo

System Properties Comparison Drizzle vs. EDB Postgres vs. FatDB 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.

The EDB Postgres Platform is an enterprise-class data management platform based on the open source database PostgreSQL with flexible deployment options and Oracle compatibility features, complemented by tool kits for management, integration, and migration.

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

TimeSeries DBMS for AIoT and BigData

Primary database model

Relational DBMS

Document store
Key-value store

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.90
Rank	#135	Overall
	#63	Relational DBMS

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Website

www.enterprisedb.com

machbase.com

Technical documentation

www.enterprisedb.com/docs

machbase.com/dbms

Developer

Drizzle project, originally started by Brian Aker

EnterpriseDB

FatCloud

Machbase

Initial release

2008

2005

2012

2013

Current release

7.2.4, September 2012

14, December 2021

V8.0, August 2023

License

Commercial or Open Source

Open Source

GNU GPL

commercial

BSD for PostgreSQL-components

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

Server operating systems

FreeBSD
Linux
OS X

Linux
Windows

Windows

Linux
macOS
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

standard with numerous extensions

Via inetgration in SQL Server

SQL-like query language

APIs and other access methods

JDBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

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

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

Supported programming languages

C
C++
Java
PHP

.Net
C
C++
Delphi
Java
Perl
PHP
Python
Tcl

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

yes

via applications

Triggers

hooks for callbacks inside the server can be used.

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

by hash, list or range

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

Can implement custom security layer via applications

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

EDB Puts Postgres in the Middle of Analytics Workflow with New Lakehouse Stack
22 April 2024, Datanami

EDB Is Developing Its Flagship Database Into A Comprehensive Platform For Analytics, AI
27 February 2024, CRN

Key new features and innovations in EDB Postgres 16
1 December 2023, InfoWorld

EDB Closes the High Availability Gap for Postgres in the Cloud with EDB Postgres Distributed on BigAnimal
29 August 2023, GlobeNewswire

EDB Introduces Two New Ways to Get Postgres in AWS Marketplace
28 November 2023, Yahoo Finance

provided by Google News

“Luxembourg is a perfect target area”: Korean accelerator exec
27 October 2022, Delano.lu

provided by Google News

Share this page