DBMS > DolphinDB vs. Firebase Realtime Database vs. GeoMesa vs. Valentina Server vs. Yanza

System Properties Comparison DolphinDB vs. Firebase Realtime Database vs. GeoMesa vs. Valentina Server vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

DolphinDB is a high performance Time Series DBMS. It is integrated with an easy-to-use fully featured programming language and a high-volume high-velocity streaming analytics system. It offers operational simplicity, scalability, fault tolerance, and concurrency.

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

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Object-relational database and reports server

Time Series DBMS for IoT Applications

Primary database model

Secondary database models

Relational DBMS

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

Score	4.13
Rank	#80	Overall
	#6	Time Series DBMS

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

www.dolphindb.com

firebase.google.com/products/realtime-database

www.geomesa.org

www.valentina-db.net

yanza.com

Technical documentation

docs.dolphindb.cn/en/help200/index.html

firebase.google.com/docs/database

www.geomesa.org/documentation/stable/user/index.html

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

DolphinDB, Inc

Google

acquired by Google 2014

CCRi and others

Paradigma Software

Yanza

Initial release

2018

2012

2014

1999

2015

Current release

v2.00.4, January 2022

4.0.5, February 2024

5.7.5

License

Commercial or Open Source

commercial

free community version available

commercial

Open Source

Apache License 2.0

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

Scala

Server operating systems

Linux
Windows

hosted

Linux
OS X
Windows

Windows

Data scheme

yes

schema-free

yes

schema-free

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

yes

APIs and other access methods

JDBC
JSON over HTTP
Kafka
MQTT (Message Queue Telemetry Transport)
ODBC
OPC DA
OPC UA
RabbitMQ
WebSocket

Android
iOS
JavaScript API
RESTful HTTP API

ODBC

HTTP API

Supported programming languages

C#
C++
Go
Java
JavaScript
MatLab
Python
R
Rust

Java
JavaScript
Objective-C

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

limited functionality with using 'rules'

yes

Triggers

Callbacks are triggered when data changes

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

depending on storage layer

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on storage layer

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

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

depending on storage layer

yes

User concepts

Access control

Administrators, Users, Groups

yes, based on authentication and database rules

yes

depending on the DBMS used for storage

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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

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

Atos cybersecurity blog: Misconfigured Firebase: A real-time cyber threat
18 January 2024, Atos

Don't be like these 900+ websites and expose millions of passwords via Firebase
18 March 2024, The Register

Google Firebase may have exposed 125M records from misconfigurations
19 March 2024, SC Media

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

provided by Google News

A Look at Valentina — SitePoint
18 April 2014, SitePoint

MySQL GUI Tools for Windows and Ubuntu/Linux: Top 8 free or open source
7 December 2018, H2S Media

provided by Google News

Share this page