DBMS > Firebase Realtime Database vs. Memcached vs. SAP HANA vs. TimescaleDB vs. VelocityDB

System Properties Comparison Firebase Realtime Database vs. Memcached vs. SAP HANA vs. TimescaleDB vs. VelocityDB

Editorial information provided by DB-Engines

Name

Description

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

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

In-memory, column based data store. Available as appliance or cloud service

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Graph DBMS
Object oriented DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Relational DBMS

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

Score	13.64
Rank	#39	Overall
	#6	Document stores

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

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Score	0.11
Rank	#354	Overall
	#37	Graph DBMS
	#15	Object oriented DBMS

Website

firebase.google.com/products/realtime-database

www.memcached.org

www.sap.com/products/hana.html

www.timescale.com

velocitydb.com

Technical documentation

firebase.google.com/docs/database

github.com/memcached/memcached/wiki

help.sap.com/hana

docs.timescale.com

velocitydb.com/UserGuide

Developer

Google

acquired by Google 2014

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

SAP

Timescale

VelocityDB Inc

Initial release

2012

2003

2010

2017

2011

Current release

1.6.27, May 2024

2.0 SPS07 (April 4, 2023), April 2023

2.15.0, May 2024

7.x

License

Commercial or Open Source

commercial

Open Source

BSD license

commercial

Open Source

Apache 2.0

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Server operating systems

hosted

FreeBSD
Linux
OS X
Unix
Windows

Appliance or cloud-service

Linux
OS X
Windows

Any that supports .NET

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data 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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

full PostgreSQL SQL syntax

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

Proprietary protocol

JDBC
ODBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

.Net

Supported programming languages

Java
JavaScript
Objective-C

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

.Net

Server-side scripts

Stored procedures

limited functionality with using 'rules'

SQLScript, R

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

Callbacks are triggered when data changes

yes

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

none

yes

yes, across time and space (hash partitioning) attributes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Repcached, a Memcached patch, provides this functionallity

yes

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

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, based on authentication and database rules

yes

using SASL (Simple Authentication and Security Layer) protocol

yes

fine grained access rights according to SQL-standard

Based on Windows 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.