DBMS > Apache Drill vs. EsgynDB vs. Google Cloud Bigtable vs. OpenEdge vs. Snowflake

System Properties Comparison Apache Drill vs. EsgynDB vs. Google Cloud Bigtable vs. OpenEdge vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Application development environment with integrated database management system

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

Primary database model

Document store
Relational DBMS

Relational DBMS

Key-value store
Wide column store

Relational DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

drill.apache.org

www.esgyn.cn

cloud.google.com/bigtable

www.progress.com/openedge

www.snowflake.com

Technical documentation

drill.apache.org/docs

cloud.google.com/bigtable/docs

documentation.progress.com/output/ua/OpenEdge_latest

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Esgyn

Google

Progress Software Corporation

Snowflake Computing Inc.

Initial release

2012

2015

1984

2014

Current release

1.20.3, January 2023

OpenEdge 12.2, March 2020

License

Commercial or Open Source

Open Source

Apache Version 2

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

Server operating systems

Linux
OS X
Windows

Linux

hosted

AIX
HP-UX
Linux
Solaris
Windows

hosted

Data scheme

schema-free

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

SQL SELECT statement is SQL:2003 compliant

yes

close to SQL 92

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

C++

All languages supporting JDBC/ODBC/ADO.Net

C#
C++
Go
Java
JavaScript (Node.js)
Python

Progress proprietary ABL (Advanced Business Language)

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Java Stored Procedures

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

since Version 11.4

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Internal replication in Colossus, and regional replication between two clusters in different zones

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

none

Immediate Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic single-row operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

User concepts

Access control

Depending on the underlying data source

fine grained access rights according to SQL-standard

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Users and groups

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.