DBMS > Drizzle vs. Kyligence Enterprise vs. MySQL vs. Teradata

System Properties Comparison Drizzle vs. Kyligence Enterprise vs. MySQL vs. Teradata

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

A distributed analytics engine for big data, built on top of Apache Kylin

Widely used open source RDBMS

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.46
Rank	#266	Overall
	#124	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	44.87
Rank	#22	Overall
	#15	Relational DBMS

Website

kyligence.io/kyligence-enterprise

www.mysql.com

www.teradata.com

Technical documentation

dev.mysql.com/doc

docs.teradata.com

Developer

Drizzle project, originally started by Brian Aker

Kyligence, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

Teradata

Initial release

2008

2016

1995

1984

Current release

7.2.4, September 2012

8.4.0, April 2024

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

Open Source

GNU GPL

commercial

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

Java

C and C++

Server operating systems

FreeBSD
Linux
OS X

Linux

FreeBSD
Linux
OS X
Solaris
Windows

hosted
Linux

Data scheme

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

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

yes

with proprietary extensions

ANSI SQL for queries (using Apache Calcite)

yes

with proprietary extensions

yes

SQL 2016 + extensions

APIs and other access methods

JDBC

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

C
C++
Java
PHP

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

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

UDFs, stored procedures, table functions in parallel

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

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

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

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.