DBMS > EsgynDB vs. HarperDB vs. IBM Cloudant vs. Snowflake

System Properties Comparison EsgynDB vs. HarperDB vs. IBM Cloudant vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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.

Database as a Service offering based on Apache CouchDB

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

Primary database model

Relational DBMS

Document store

Relational DBMS

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	0.55
Rank	#248	Overall
	#38	Document stores

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.esgyn.cn

www.harperdb.io

www.ibm.com/products/cloudant

www.snowflake.com

Technical documentation

docs.harperdb.io/docs

cloud.ibm.com/docs/Cloudant

docs.snowflake.net/manuals/index.html

Developer

Esgyn

HarperDB

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Snowflake Computing Inc.

Initial release

2015

2017

2010

2014

Current release

3.1, August 2021

License

Commercial or Open Source

commercial

free community edition 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

C++, Java

Node.js

Erlang

Server operating systems

Linux

Linux
OS X

hosted

Data scheme

yes

dynamic schema

schema-free

yes

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

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like data manipulation statements

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

.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#
Java
JavaScript
Objective-C
PHP
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Java Stored Procedures

Custom Functions

since release 3.1

View functions (Map-Reduce) in JavaScript

user defined functions

Triggers

yes

similar concept for controling cloud resources

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

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

yes

the nodes on which a table resides can be defined

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

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

Atomic execution of specific operations

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

yes, using LMDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles

Access rights for users can be defined per database

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.