DBMS > Apache Doris vs. MySQL vs. OpenEdge vs. searchxml

System Properties Comparison Apache Doris vs. MySQL vs. OpenEdge vs. searchxml

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An MPP-based analytics DBMS embracing the MySQL protocol

Widely used open source RDBMS

Application development environment with integrated database management system

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Native XML DBMS
Search engine

Secondary database models

Document store
Spatial DBMS

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

Score	0.61
Rank	#235	Overall
	#110	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	3.69
Rank	#78	Overall
	#42	Relational DBMS

Score	0.00
Rank	#385	Overall
	#7	Native XML DBMS
	#24	Search engines

Website

doris.apache.org
github.com/apache/doris

www.mysql.com

www.progress.com/openedge

www.searchxml.net/category/products

Technical documentation

github.com/apache/doris/wiki

dev.mysql.com/doc

documentation.progress.com/output/ua/OpenEdge_latest

www.searchxml.net/support/handouts

Developer

Apache Software Foundation, originally contributed from Baidu

Oracle

since 2010, originally MySQL AB, then Sun

Progress Software Corporation

informationpartners gmbh

Initial release

2017

1995

1984

2015

Current release

1.2.2, February 2023

9.0.0, July 2024

OpenEdge 12.2, March 2020

1.0

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

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

C and C++

C++

Server operating systems

Linux

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
Solaris
Windows

Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

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

with proprietary extensions

yes

close to SQL 92

APIs and other access methods

JDBC
MySQL client

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

Java

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

Progress proprietary ABL (Advanced Business Language)

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

yes

on the application server

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

since Version 11.4

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

Source-replica replication

yes

sychronisation to multiple collections

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

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

multiple readers, single writer

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

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

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

Users and groups

Domain, group and role-based access control at the document level and for application services

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.