DBMS > Apache Impala vs. CouchDB vs. Google Cloud Datastore vs. Microsoft SQL Server vs. Tigris

System Properties Comparison Apache Impala vs. CouchDB vs. Google Cloud Datastore vs. Microsoft SQL Server vs. Tigris

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.

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Microsofts flagship relational DBMS

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Relational DBMS

Document store

Relational DBMS

Document store
Key-value store
Search engine
Time Series DBMS

Secondary database models

Document store

Spatial DBMS

using the Geocouch extension

Document store
Graph DBMS
Spatial DBMS

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	4.47
Rank	#76	Overall
	#12	Document stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.02
Rank	#369	Overall
	#51	Document stores
	#55	Key-value stores
	#24	Search engines
	#38	Time Series DBMS

Website

impala.apache.org

couchdb.apache.org

cloud.google.com/datastore

www.microsoft.com/en-us/sql-server

www.tigrisdata.com

Technical documentation

impala.apache.org/impala-docs.html

docs.couchdb.org/en/stable

cloud.google.com/datastore/docs

learn.microsoft.com/en-US/sql/sql-server

www.tigrisdata.com/docs

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

Google

Microsoft

Tigris Data, Inc.

Initial release

2013

2005

2008

1989

2022

Current release

4.1.0, June 2022

3.3.3, December 2023

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache version 2

commercial

restricted free version is available

Open Source

Apache Version 2.0

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

C++

Erlang

C++

Server operating systems

Linux

Android
BSD
Linux
OS X
Solaris
Windows

hosted

Linux
Windows

Linux
macOS
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

SQL-like query language (GQL)

yes

APIs and other access methods

JDBC
ODBC

RESTful HTTP/JSON API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

CLI Client
gRPC
RESTful HTTP API

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

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Go
Java
JavaScript (Node.js)

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

View functions in JavaScript

using Google App Engine

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

Multi-source replication using Paxos

yes, but depending on the SQL-Server Edition

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

atomic operations within a single document possible

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Durability

Support for making data persistent

yes

yes, using FoundationDB

In-memory capabilities

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

yes

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

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

fine grained access rights according to SQL-standard

Access rights for users and roles

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.