DBMS > Apache Kylin vs. etcd vs. MySQL vs. OpenEdge

System Properties Comparison Apache Kylin vs. etcd vs. MySQL vs. OpenEdge

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed analytics engine for big data, providing a SQL interface and multi-dimensional analysis (OLAP) and leveraging the Hadoop stack

A distributed reliable key-value store

Widely used open source RDBMS

Application development environment with integrated database management system

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.14
Rank	#171	Overall
	#77	Relational DBMS

Score	7.05
Rank	#53	Overall
	#5	Key-value stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	3.69
Rank	#78	Overall
	#42	Relational DBMS

Website

kylin.apache.org

etcd.io
github.com/etcd-io/etcd

www.mysql.com

www.progress.com/openedge

Technical documentation

kylin.apache.org/docs

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

dev.mysql.com/doc

documentation.progress.com/output/ua/OpenEdge_latest

Developer

Apache Software Foundation, originally contributed from eBay Inc

Oracle

since 2010, originally MySQL AB, then Sun

Progress Software Corporation

Initial release

2015

1995

1984

Current release

3.1.0, July 2020

3.4, August 2019

9.0.0, July 2024

OpenEdge 12.2, March 2020

License

Commercial or Open Source

Open Source

Apache Version 2.0

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

Server operating systems

Linux

FreeBSD
Linux
Windows

experimental

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

yes

schema-free

yes

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

ANSI SQL for queries (using Apache Calcite)

yes

with proprietary extensions

yes

close to SQL 92

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

gRPC
JSON over HTTP

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC

Supported programming languages

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

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)

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Triggers

yes, watching key changes

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

since Version 11.4

Replication methods

Methods for redundantly storing data on multiple nodes

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

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

Users with fine-grained authorization concept

no user groups or roles

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.