DBMS > Apache Impala vs. CouchDB vs. EJDB vs. Microsoft Azure Synapse Analytics vs. Snowflake

System Properties Comparison Apache Impala vs. CouchDB vs. EJDB vs. Microsoft Azure Synapse Analytics vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Elastic, large scale data warehouse service leveraging the broad eco-system of SQL Server

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

Primary database model

Relational DBMS

Document store

Relational DBMS

Secondary database models

Document store

Spatial DBMS

using the Geocouch extension

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	20.56
Rank	#31	Overall
	#19	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

impala.apache.org

couchdb.apache.org

github.com/Softmotions/ejdb

azure.microsoft.com/services/synapse-analytics

www.snowflake.com

Technical documentation

impala.apache.org/impala-docs.html

docs.couchdb.org/en/stable

github.com/Softmotions/ejdb/blob/master/README.md

docs.microsoft.com/azure/synapse-analytics

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Apache Software Foundation

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

Softmotions

Microsoft

Snowflake Computing Inc.

Initial release

2013

2005

2012

2016

2014

Current release

4.1.0, June 2022

3.3.3, December 2023

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache version 2

Open Source

GPLv2

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++

Erlang

C++

Server operating systems

Linux

Android
BSD
Linux
OS X
Solaris
Windows

server-less

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

string, integer, double, bool, date, object_id

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-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC

RESTful HTTP/JSON API

in-process shared library

ADO.NET
JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

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

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C#
Java
PHP

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

View functions in JavaScript

Transact SQL

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

none

Sharding, horizontal partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints

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

Read/Write 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.

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Access rights for users can be defined per database

yes

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.