DBMS > Apache Impala vs. Google Cloud Firestore vs. Prometheus vs. Riak KV vs. SQLite

System Properties Comparison Apache Impala vs. Google Cloud Firestore vs. Prometheus vs. Riak KV vs. SQLite

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.

Open-source Time Series DBMS and monitoring system

Distributed, fault tolerant key-value store

Widely used embeddable, in-process RDBMS

Primary database model

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

Secondary database models

Document store

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

impala.apache.org

firebase.google.com/products/firestore

prometheus.io

www.sqlite.org

Technical documentation

impala.apache.org/impala-docs.html

firebase.google.com/docs/firestore

prometheus.io/docs

www.tiot.jp/riak-docs/riak/kv/latest

www.sqlite.org/docs.html

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Google

OpenSource, formerly Basho Technologies

Dwayne Richard Hipp

Initial release

2013

2017

2015

2009

2000

Current release

4.1.0, June 2022

3.2.0, December 2022

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

Apache 2.0

Open Source

Apache version 2, commercial enterprise edition

Open Source

Public Domain

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

Server operating systems

Linux

hosted

Linux
Windows

Linux
OS X

server-less

Data scheme

yes

schema-free

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

Numeric data only

yes

not rigid because of 'dynamic typing' concept.

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.

Import of XML data possible

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC

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

RESTful HTTP/JSON API

HTTP API
Native Erlang Interface

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

All languages supporting JDBC/ODBC

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

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes, Firebase Rules & Cloud Functions

Erlang

Triggers

yes, with Cloud Functions

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

yes

by Federation

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Using Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

none

Eventual Consistency

Foreign keys

Referential integrity

links between data sets can be stored

yes

Transaction concepts

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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 Riak Security

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.