DBMS > Apache Impala vs. BigchainDB vs. etcd vs. Google Cloud Firestore vs. Microsoft SQL Server

System Properties Comparison Apache Impala vs. BigchainDB vs. etcd vs. Google Cloud Firestore vs. Microsoft SQL Server

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

Microsofts flagship relational DBMS

Primary database model

Secondary database models

Document store

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	0.79
Rank	#212	Overall
	#36	Document stores

Score	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Website

impala.apache.org

www.bigchaindb.com

etcd.io
github.com/etcd-io/etcd

firebase.google.com/products/firestore

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

Technical documentation

impala.apache.org/impala-docs.html

bigchaindb.readthedocs.io/en/latest

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

firebase.google.com/docs/firestore

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

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Google

Microsoft

Initial release

2013

2016

2017

1989

Current release

4.1.0, June 2022

3.4, August 2019

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

AGPL v3

Open Source

Apache Version 2.0

commercial

restricted free version is available

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

Python

C++

Server operating systems

Linux

FreeBSD
Linux
Windows

experimental

hosted

Linux
Windows

Data scheme

yes

schema-free

yes

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

yes

APIs and other access methods

JDBC
ODBC

CLI Client
RESTful HTTP API

gRPC
JSON over HTTP

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

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

Supported programming languages

All languages supporting JDBC/ODBC

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

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

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes, Firebase Rules & Cloud Functions

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

Triggers

yes, watching key changes

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

Multi-source replication

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes,with MongoDB ord RethinkDB

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

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

yes

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

fine grained access rights according to SQL-standard

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.