DBMS > Drizzle vs. Firebase Realtime Database vs. Graph Engine vs. STSdb

System Properties Comparison Drizzle vs. Firebase Realtime Database vs. Graph Engine vs. STSdb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Relational DBMS

Document store

Graph DBMS
Key-value store

Key-value store

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

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	0.10
Rank	#357	Overall
	#51	Key-value stores

Website

firebase.google.com/products/realtime-database

www.graphengine.io

github.com/STSSoft/STSdb4

Technical documentation

firebase.google.com/docs/database

www.graphengine.io/docs/manual

Developer

Drizzle project, originally started by Brian Aker

Google

acquired by Google 2014

Microsoft

STS Soft SC

Initial release

2008

2012

2010

2011

Current release

7.2.4, September 2012

4.0.8, September 2015

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

MIT License

Open Source

GPLv2, commercial license 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++

.NET and C

Server operating systems

FreeBSD
Linux
OS X

hosted

.NET

Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

yes

with proprietary extensions

APIs and other access methods

JDBC

Android
iOS
JavaScript API
RESTful HTTP API

RESTful HTTP API

.NET Client API

Supported programming languages

C
C++
Java
PHP

Java
JavaScript
Objective-C

C#
C++
F#
Visual Basic

C#
Java

Server-side scripts

Stored procedures

limited functionality with using 'rules'

yes

Triggers

hooks for callbacks inside the server can be used.

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

yes, based on authentication and database rules

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

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

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

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 launches Firebase Genkit, a new open source framework for building AI-powered apps
14 May 2024, TechCrunch

Hundreds of Google Firebase websites might have leaked data online
19 March 2024, TechRadar

provided by Google News

Trinity
30 October 2010, Microsoft

Open source Microsoft Graph Engine takes on Neo4j
13 February 2017, InfoWorld

IBM releases Graph, a service that can outperform SQL databases
27 July 2016, GeekWire

The graph analytics landscape 2019 - DataScienceCentral.com
27 February 2019, Data Science Central

Aerospike Is Now a Graph Database, Too
21 June 2023, Datanami

provided by Google News

Share this page