DBMS > Apache Impala vs. Google Cloud Firestore vs. Memcached vs. Snowflake vs. TerarkDB

System Properties Comparison Apache Impala vs. Google Cloud Firestore vs. Memcached vs. Snowflake vs. TerarkDB

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

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.

In-memory key-value store, originally intended for caching

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

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Secondary database models

Document store

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

Score	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	7.36
Rank	#53	Overall
	#9	Document stores

Score	18.08
Rank	#32	Overall
	#4	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.08
Rank	#367	Overall
	#56	Key-value stores

Website

impala.apache.org

firebase.google.com/products/firestore

www.memcached.org

www.snowflake.com

github.com/bytedance/terarkdb

Technical documentation

impala.apache.org/impala-docs.html

firebase.google.com/docs/firestore

github.com/memcached/memcached/wiki

docs.snowflake.net/manuals/index.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Google

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Snowflake Computing Inc.

ByteDance, originally Terark

Initial release

2013

2017

2003

2014

2016

Current release

4.1.0, June 2022

1.6.27, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

BSD license

commercial

restricted open source version 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++

Server operating systems

Linux

hosted

FreeBSD
Linux
OS X
Unix
Windows

hosted

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

schema-free

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

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

Proprietary protocol

CLI Client
JDBC
ODBC

C++ API
Java API

Supported programming languages

All languages supporting JDBC/ODBC

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

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

C++
Java

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes, Firebase Rules & Cloud Functions

user defined functions

Triggers

yes, with Cloud Functions

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

none

Repcached, a Memcached patch, provides this functionallity

yes

none

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

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, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

yes

using SASL (Simple Authentication and Security Layer) protocol

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.