DBMS > OpenEdge vs. QuestDB vs. Sphinx vs. SQLite

System Properties Comparison OpenEdge vs. QuestDB vs. Sphinx 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 search engine for searching in data from different sources, e.g. relational databases

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Relational DBMS

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

Score	3.75
Rank	#88	Overall
	#47	Relational DBMS

Score	2.48
Rank	#115	Overall
	#9	Time Series DBMS

Score	6.03
Rank	#60	Overall
	#6	Search engines

Score	116.01
Rank	#10	Overall
	#7	Relational DBMS

Website

www.progress.com/openedge

questdb.io

sphinxsearch.com

www.sqlite.org

Technical documentation

documentation.progress.com/output/ua/OpenEdge_latest

questdb.io/docs

sphinxsearch.com/docs

www.sqlite.org/docs.html

Developer

Progress Software Corporation

QuestDB Technology Inc

Sphinx Technologies Inc.

Dwayne Richard Hipp

Initial release

1984

2014

2001

2000

Current release

OpenEdge 12.2, March 2020

3.5.1, February 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

GPL version 2, commercial licence 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

C++

Server operating systems

AIX
HP-UX
Linux
Solaris
Windows

Linux
macOS
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

server-less

Data scheme

yes

schema-free via InfluxDB Line Protocol

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

full-text index on all search fields

yes

SQL

Support of SQL

yes

close to SQL 92

SQL with time-series extensions

SQL-like query language (SphinxQL)

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

Proprietary protocol

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

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

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

Partitioning is done manually, search queries against distributed index is supported

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Source-replica replication with eventual consistency

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

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

More information provided by the system vendor

Specific characteristics

Relational model with native time series support Column-based storage and time partitioned...
» more

Competitive advantages

High ingestion throughput: peak of 4M rows/sec (TSBS Benchmark) Code optimizations...
» more

Typical application scenarios

Financial tick data Industrial IoT Application Metrics Monitoring
» more

Key customers

Banks & Hedge funds, Yahoo, OKX, Airbus, Aquis Exchange, Net App, Cloudera, Airtel,...
» more

Licensing and pricing models

Open source Apache 2.0 QuestDB Enterprise QuestDB Cloud
» more

News

Does "vpmovzxbd" Scare You? Here's Why it Doesn't Have To
12 April 2024

Create an ADS-B flight radar with QuestDB and a Raspberry Pi
8 April 2024

Build a temperature IoT sensor with Raspberry Pi Pico & QuestDB
5 April 2024

Create an IoT server with QuestDB and a Raspberry Pi
4 April 2024

TimescaleDB vs. QuestDB: Performance benchmarks and overview
27 March 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.