DBMS > Apache IoTDB vs. FatDB vs. Google Cloud Firestore vs. Linter

System Properties Comparison Apache IoTDB vs. FatDB vs. Google Cloud Firestore vs. Linter

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

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

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.

RDBMS for high security requirements

Primary database model

Time Series DBMS

Document store
Key-value store

Document store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	1.31
Rank	#159	Overall
	#14	Time Series DBMS

Score	6.63
Rank	#54	Overall
	#9	Document stores

Score	0.03
Rank	#368	Overall
	#156	Relational DBMS

Website

iotdb.apache.org

firebase.google.com/products/firestore

linter.ru

Technical documentation

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

firebase.google.com/docs/firestore

Developer

Apache Software Foundation

FatCloud

Google

relex.ru

Initial release

2018

2012

2017

1990

Current release

1.1.0, April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

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

Java

C and C++

Server operating systems

All OS with a Java VM (>= 1.8)

Windows

hosted

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

Via inetgration in SQL Server

yes

APIs and other access methods

JDBC
Native API

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

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

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

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

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

Server-side scripts

Stored procedures

yes

via applications

yes, Firebase Rules & Cloud Functions

yes

proprietary syntax with the possibility to convert from PL/SQL

Triggers

yes

via applications

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

selectable replication factor

Multi-source replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Eventual Consistency
Immediate 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

yes

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.

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.

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

Recent citations in the news

AMD Zen 5 Not Affected By Inception/SRSO, mitigations=off Yields No Benefit On Ryzen 9000 Series
6 September 2024, Phoronix

TsFile: A Standard Format for IoT Time Series Data
27 February 2024, The New Stack

AMD EPYC 8534P / EPYC 8534PN Benchmarks - Siena Delivers Incredible Value & Energy Efficiency For Linux Servers Review
29 November 2023, Phoronix

Apache Promotes IoT Database Project
25 September 2020, Datanami

IoTDB Provides Data Management for Industrial Edge IT
15 October 2020, The New Stack

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’s NoSQL database service Cloud Firestore now up for grabs
1 February 2019, Daily Host News

provided by Google News

Share this page