DBMS > AgensGraph vs. Firebase Realtime Database vs. Microsoft Azure Cosmos DB vs. TDengine

System Properties Comparison AgensGraph vs. Firebase Realtime Database vs. Microsoft Azure Cosmos DB vs. TDengine

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

Globally distributed, horizontally scalable, multi-model database service

Time Series DBMS and big data platform

Primary database model

Graph DBMS
Relational DBMS

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Secondary database models

Spatial DBMS

Relational DBMS

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

Score	0.20
Rank	#321	Overall
	#27	Graph DBMS
	#143	Relational DBMS

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	2.60
Rank	#107	Overall
	#8	Time Series DBMS

Website

bitnine.net/agensgraph

firebase.google.com/products/realtime-database

azure.microsoft.com/services/cosmos-db

github.com/taosdata/TDengine
tdengine.com

Technical documentation

bitnine.net/documentation

firebase.google.com/docs/database

learn.microsoft.com/azure/cosmos-db

docs.tdengine.com

Developer

Bitnine Global Inc.

Google

acquired by Google 2014

Microsoft

TDEngine, previously Taos Data

Initial release

2016

2012

2014

2019

Current release

2.1, December 2018

3.0, August 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

AGPL V3, also commercial editions 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

Server operating systems

Linux
OS X
Windows

hosted

Linux
Windows

Data scheme

depending on used data model

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

SQL

Support of SQL

yes

SQL-like query language

Standard SQL with extensions for time-series applications

APIs and other access methods

Cypher Query Language
JDBC

Android
iOS
JavaScript API
RESTful HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

JDBC
RESTful HTTP API

Supported programming languages

C
Java
JavaScript
Python

Java
JavaScript
Objective-C

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Rust

Server-side scripts

Stored procedures

yes

limited functionality with using 'rules'

JavaScript

Triggers

Callbacks are triggered when data changes

JavaScript

yes, via alarm monitoring

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Implicit feature of the cloud service

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

Multi-item ACID transactions with snapshot isolation within a partition

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

fine grained access rights according to SQL-standard

yes, based on authentication and database rules

Access rights can be defined down to the item level

yes

More information provided by the system vendor

Specific characteristics

TDengine™ is a next generation data historian purpose-built for Industry 4.0 and...
» more

Competitive advantages

High Performance at any Scale: TDengine is purpose-built for handling massive industrial...
» more

Typical application scenarios

TDengine is designed for Industrial IoT scenarios, including: Manufacturing Connected...
» more

Market metrics

TDengine has garnered over 22,500 stars on GitHub and is used in over 50 countries...
» more

Licensing and pricing models

TDengine OSS is an open source, cloud native time series database. It includes built-in...
» more

News

Can Typical Time-Series Databases Replace Data Historians?
8 May 2024

TDengine 3.3.0.0 Release Notes
7 May 2024

How to Unlock Value from Industrial Data with AI and ML Technology
6 May 2024

Compare InfluxDB vs. TDengine
19 April 2024

Why We Need the Next Generation Data Historian
15 April 2024

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.