DBMS > Dolt vs. Firebase Realtime Database vs. OpenEdge vs. Quasardb vs. SQLite

System Properties Comparison Dolt vs. Firebase Realtime Database vs. OpenEdge vs. Quasardb vs. SQLite

Editorial information provided by DB-Engines

Name

Description

A MySQL compatible DBMS with Git-like versioning of data and schema

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

Application development environment with integrated database management system

Distributed, high-performance timeseries database

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Document store

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

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	3.45
Rank	#85	Overall
	#46	Relational DBMS

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

github.com/dolthub/dolt
www.dolthub.com

firebase.google.com/products/realtime-database

www.progress.com/openedge

quasar.ai

www.sqlite.org

Technical documentation

docs.dolthub.com

firebase.google.com/docs/database

documentation.progress.com/output/ua/OpenEdge_latest

doc.quasar.ai/master

www.sqlite.org/docs.html

Developer

DoltHub Inc

Google

acquired by Google 2014

Progress Software Corporation

quasardb

Dwayne Richard Hipp

Initial release

2018

2012

1984

2009

2000

Current release

OpenEdge 12.2, March 2020

3.14.1, January 2024

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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

Linux
macOS
Windows

hosted

AIX
HP-UX
Linux
Solaris
Windows

BSD
Linux
OS X
Windows

server-less

Data scheme

yes

schema-free

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

integer and binary

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

with tags

yes

SQL

Support of SQL

yes

close to SQL 92

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

CLI Client
HTTP REST

Android
iOS
JavaScript API
RESTful HTTP API

JDBC
ODBC

HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Java
JavaScript
Objective-C

Progress proprietary ABL (Advanced Business Language)

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

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

yes

currently in alpha release

limited functionality with using 'rules'

yes

Triggers

yes

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

since Version 11.4

Sharding

consistent hashing

none

Replication methods

Methods for redundantly storing data on multiple nodes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Source-replica replication

Source-replica replication with selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

by using LevelDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Transient mode

yes

User concepts

Access control

Only one user is configurable, and must be specified in the config file at startup

yes, based on authentication and database rules

Users and groups

Cryptographically strong user authentication and audit trail

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.