DBMS > Apache Kylin vs. CouchDB vs. Ingres vs. MySQL

System Properties Comparison Apache Kylin vs. CouchDB vs. Ingres vs. MySQL

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 native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

Well established RDBMS

Widely used open source RDBMS

Primary database model

Relational DBMS

Document store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Spatial DBMS

using the Geocouch extension

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.46
Rank	#51	Overall
	#7	Document stores

Score	3.63
Rank	#79	Overall
	#43	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

kylin.apache.org

couchdb.apache.org

www.actian.com/databases/ingres

www.mysql.com

Technical documentation

kylin.apache.org/docs

docs.couchdb.org/en/stable

docs.actian.com/ingres

dev.mysql.com/doc

Developer

Apache Software Foundation, originally contributed from eBay Inc

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Actian Corporation

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2015

2005

1974

originally developed at University Berkely in early 1970s

1995

Current release

3.1.0, July 2020

3.3.3, December 2023

12.0, July 2024

9.0.0, July 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache version 2

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

Erlang

C and C++

Server operating systems

Linux

Android
BSD
Linux
OS X
Solaris
Windows

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

FreeBSD
Linux
OS X
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.

but tools for importing/exporting data from/to XML-files available

yes

Secondary indexes

yes

via views

yes

SQL

Support of SQL

ANSI SQL for queries (using Apache Calcite)

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

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

Server-side scripts

Stored procedures

View functions in JavaScript

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

horizontal partitioning

Ingres Star to access multiple databases simultaneously

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Ingres Replicator

Multi-source 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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

atomic operations within a single document possible

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

MVCC

yes

table locks or row locks depending on storage engine

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

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.