DBMS > Apache Impala vs. FatDB vs. Google Cloud Firestore vs. Splunk

System Properties Comparison Apache Impala vs. FatDB vs. Google Cloud Firestore vs. Splunk

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

Analytic DBMS for Hadoop

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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.

Analytics Platform for Big Data

Primary database model

Relational DBMS

Document store
Key-value store

Document store

Search engine

Secondary database models

Document store

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

Score	10.63
Rank	#40	Overall
	#24	Relational DBMS

Score	6.63
Rank	#54	Overall
	#9	Document stores

Score	93.02
Rank	#13	Overall
	#2	Search engines

Website

impala.apache.org

firebase.google.com/products/firestore

www.splunk.com

Technical documentation

impala.apache.org/impala-docs.html

firebase.google.com/docs/firestore

docs.splunk.com/Documentation/Splunk

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

FatCloud

Google

Splunk Inc.

Initial release

2013

2012

2017

2003

Current release

4.1.0, June 2022

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Limited free edition and free developer edition 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

Windows

hosted

Linux
OS X
Solaris
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

Via inetgration in SQL Server

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC
ODBC

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

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

HTTP REST

Supported programming languages

All languages supporting JDBC/ODBC

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

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

via applications

yes, Firebase Rules & Cloud Functions

yes

Triggers

yes

via applications

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Using Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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.

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Can implement custom security layer via applications

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

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Cloud-based DBMS's popularity grows at high rates
12 December 2019, Paul Andlinger

show all

Enterprise Search Engines almost double their popularity in the last 12 months
2 July 2014, Paul Andlinger

show all

Recent citations in the news

Apache Impala 4 Supports Operator Multi-Threading
29 July 2021, iProgrammer

Apache Impala becomes Top-Level Project
28 November 2017, SDTimes.com

Cloudera brings Apache Iceberg data lake format to its Data Platform
30 June 2022, SiliconANGLE News

Hudi: Uber Engineering’s Incremental Processing Framework on Apache Hadoop
12 March 2017, Uber

Updates & Upserts in Hadoop Ecosystem with Apache Kudu
27 October 2017, KDnuggets

provided by Google News

Realtime vs Cloud Firestore: Which Firebase Database to Choose
8 March 2024, Appinventiv

Google's AI-First Strategy Brings Vector Support To Cloud Databases
1 March 2024, Forbes

Google launches Firebase Genkit, a new open source framework for building AI-powered apps
14 May 2024, TechCrunch

NoSQL on the Cloud With Python
7 August 2020, Towards Data Science

Google Launches Cloud NoSQL Database for Mobile, Web Apps
10 October 2017, ADT Magazine

provided by Google News

Share this page