DBMS > IBM Cloudant vs. Machbase Neo vs. MySQL vs. Snowflake

System Properties Comparison IBM Cloudant vs. Machbase Neo vs. MySQL vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Database as a Service offering based on Apache CouchDB

TimeSeries DBMS for AIoT and BigData

Widely used open source RDBMS

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

Primary database model

Document store

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	2.85
Rank	#95	Overall
	#18	Document stores

Score	0.07
Rank	#348	Overall
	#34	Time Series DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

www.ibm.com/products/cloudant

machbase.com

www.mysql.com

www.snowflake.com

Technical documentation

cloud.ibm.com/docs/Cloudant

machbase.com/dbms

dev.mysql.com/doc

docs.snowflake.net/manuals/index.html

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Machbase

Oracle

since 2010, originally MySQL AB, then Sun

Snowflake Computing Inc.

Initial release

2010

2013

1995

2014

Current release

V8.0, August 2023

9.0.0, July 2024

License

Commercial or Open Source

commercial

free test version available

Open Source

GPL version 2. Commercial licenses with extended functionallity are 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

C and C++

Server operating systems

hosted

Linux
macOS
Windows

FreeBSD
Linux
OS X
Solaris
Windows

hosted

Data scheme

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

SQL-like query language

yes

with proprietary extensions

yes

APIs and other access methods

RESTful HTTP/JSON API

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

ADO.NET
JDBC
ODBC
Proprietary native API

CLI Client
JDBC
ODBC

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

yes

proprietary syntax

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor

Multi-source replication
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

not for MyISAM storage engine

yes

Transaction concepts

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

atomic operations within a document possible

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

table locks or row locks depending on storage engine

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

yes

User concepts

Access control

Access rights for users can be defined per database

simple password-based access control

Users with fine-grained authorization concept

no user groups or 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.