DBMS > OpenEdge vs. QuestDB vs. RavenDB vs. SQLite

System Properties Comparison OpenEdge vs. QuestDB vs. RavenDB vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

A high performance open source SQL database for time series data

Open Source Operational and Transactional Enterprise NoSQL Document Database

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Relational DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	3.69
Rank	#78	Overall
	#42	Relational DBMS

Score	2.81
Rank	#98	Overall
	#7	Time Series DBMS

Score	2.68
Rank	#102	Overall
	#19	Document stores

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

www.progress.com/openedge

questdb.io

ravendb.net

www.sqlite.org

Technical documentation

documentation.progress.com/output/ua/OpenEdge_latest

questdb.io/docs

ravendb.net/docs

www.sqlite.org/docs.html

Developer

Progress Software Corporation

QuestDB Technology Inc

Hibernating Rhinos

Dwayne Richard Hipp

Initial release

1984

2014

2010

2000

Current release

OpenEdge 12.2, March 2020

5.4, July 2022

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

AGPL version 3, commercial license available

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java (Zero-GC), C++, Rust

Server operating systems

AIX
HP-UX
Linux
Solaris
Windows

Linux
macOS
Windows

Linux
macOS
Raspberry Pi
Windows

server-less

Data scheme

yes

schema-free via InfluxDB Line Protocol

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

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

SQL

Support of SQL

yes

close to SQL 92

SQL with time-series extensions

SQL-like query language (RQL)

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Progress proprietary ABL (Advanced Business Language)

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

since Version 11.4

horizontal partitioning (by timestamps)

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Source-replica replication with eventual consistency

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID for single-table writes

ACID, Cluster-wide transaction available

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

through memory mapped files

yes

User concepts

Access control

Users and groups

Authorization levels configured per client per database

More information provided by the system vendor

News

Combine Java and Rust Code Coverage in a Polyglot Project
10 September 2024

Weather data visualization and forecasting with QuestDB, Kafka and Grafana
4 September 2024

Building a new vector based storage model
22 August 2024

Calibrating VWAP executions with QuestDB and Grafana
16 August 2024

Write Time: a call for community writers
13 August 2024

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.