DBMS > Apache Drill vs. CouchDB vs. Kingbase vs. Snowflake

System Properties Comparison Apache Drill vs. CouchDB vs. Kingbase vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

An enterprise-class RDBMS compatible with PostgreSQL and Oracle and widely used in China.

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

Primary database model

Document store
Relational DBMS

Document store

Relational DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

Document store
Spatial DBMS

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

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	0.50
Rank	#257	Overall
	#119	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

Technical documentation

drill.apache.org/docs

docs.couchdb.org/en/stable

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

BeiJing KINGBASE Information technologies inc.

Snowflake Computing Inc.

Initial release

2012

2005

1999

2014

Current release

1.20.3, January 2023

3.3.3, December 2023

V8.0, August 2021

License

Commercial or Open Source

Open Source

Apache Version 2

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

Erlang

C and Java

Server operating systems

Linux
OS X
Windows

Android
BSD
Linux
OS X
Solaris
Windows

Linux
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

via views

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

Standard with numerous extensions

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

ADO.NET
gokb
JDBC
kdbndp
ODBC
PDI
PDO
Pro*C
psycopg2
QT

CLI Client
JDBC
ODBC

Supported programming languages

C++

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

.Net
C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

View functions in JavaScript

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

horizontal partitioning (by range, list and hash) and vertical partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

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

none

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

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.