DBMS > Dolt vs. IBM Cloudant vs. Machbase Neo vs. Netezza vs. Snowflake

System Properties Comparison Dolt vs. IBM Cloudant vs. Machbase Neo vs. Netezza vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

A MySQL compatible DBMS with Git-like versioning of data and schema

Database as a Service offering based on Apache CouchDB

TimeSeries DBMS for AIoT and BigData

Data warehouse and analytics appliance part of IBM PureSystems

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

Primary database model

Secondary database models

Document store

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

Score	0.96
Rank	#193	Overall
	#90	Relational DBMS

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	9.06
Rank	#46	Overall
	#29	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

github.com/dolthub/dolt
www.dolthub.com

www.ibm.com/products/cloudant

machbase.com

www.ibm.com/products/netezza

www.snowflake.com

Technical documentation

docs.dolthub.com

cloud.ibm.com/docs/Cloudant

machbase.com/dbms

docs.snowflake.net/manuals/index.html

Developer

DoltHub Inc

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Machbase

IBM

Snowflake Computing Inc.

Initial release

2018

2010

2013

2000

2014

Current release

V8.0, August 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

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

Erlang

Server operating systems

Linux
macOS
Windows

hosted

Linux
macOS
Windows

Linux

included in appliance

hosted

Data scheme

yes

schema-free

yes

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

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

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

CLI Client
HTTP REST

RESTful HTTP/JSON API

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

JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

C
C++
Fortran
Java
Lua
Perl
Python
R

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

currently in alpha release

View functions (Map-Reduce) in JavaScript

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Multi-source replication
Source-replica replication

selectable replication factor

Source-replica replication

yes

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

Only one user is configurable, and must be specified in the config file at startup

Access rights for users can be defined per database

simple password-based access control

Users with fine-grained authorization concept

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.