DBMS > Firebase Realtime Database vs. KeyDB vs. OpenEdge vs. SQLite

System Properties Comparison Firebase Realtime Database vs. KeyDB vs. OpenEdge vs. SQLite

Please select another system to include it in the comparison.

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.

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Application development environment with integrated database management system

Widely used embeddable, in-process RDBMS

Primary database model

Document store

Key-value store

Relational DBMS

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	0.71
Rank	#226	Overall
	#33	Key-value stores

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

firebase.google.com/products/realtime-database

github.com/Snapchat/KeyDB
keydb.dev

www.progress.com/openedge

www.sqlite.org

Technical documentation

firebase.google.com/docs/database

docs.keydb.dev

documentation.progress.com/output/ua/OpenEdge_latest

www.sqlite.org/docs.html

Developer

Google

acquired by Google 2014

EQ Alpha Technology Ltd.

Progress Software Corporation

Dwayne Richard Hipp

Initial release

2012

2019

1984

2000

Current release

OpenEdge 12.2, March 2020

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

BSD-3

commercial

Open Source

Public Domain

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++

Server operating systems

hosted

Linux

AIX
HP-UX
Linux
Solaris
Windows

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

yes

not rigid because of 'dynamic typing' concept.

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

by using the Redis Search module

yes

SQL

Support of SQL

yes

close to SQL 92

yes

SQL-92 is not fully supported

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

Proprietary protocol

RESP - REdis Serialization Protoco

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Java
JavaScript
Objective-C

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

Progress proprietary ABL (Advanced Business Language)

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

limited functionality with using 'rules'

Lua

yes

Triggers

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

since Version 11.4

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica 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

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

Optimistic locking, atomic execution of commands blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

simple password-based access control and ACL

Users and groups

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.