MySQL vs MariaDB. Where are we now?

Transcription

1

2 MySQL vs MariaDB Where are we now?

3 Hey!

4 A BRIEF HISTORY OF THE UNIVERSE (of MySQL and MariaDB)

5 Herman Hollerith

6 Unireg Begins Essentially, the origin of what we know MySQL as today, establishing its code base (~1979)

7 Unireg Begins 1995 Essentially, the origin of what we know MySQL as today, establishing its code base. MySQL is released In 1995, MySQL was first released for usage under dual licensing (~1979)

8 Unireg Begins Essentially, the origin of what we know MySQL as today, establishing its code base MySQL Goes Open The MySQL platform goes Open Source, and begins to follow the terms of the GPL. MySQL is released In 1995, MySQL was first released for usage under dual licensing (~1979) 2000

9 Unireg Begins 1995 MySQL Goes Open 2008 Essentially, the origin of what we know MySQL as today, establishing its code base. The MySQL platform goes Open Source, and begins to follow the terms of the GPL. MySQL is released Sun Acquires MySQL In 1995, MySQL was first released for usage under dual licensing. Sun Microsystems purchases MySQL AB for $1 billion (only to be acquired by Oracle in 2009 for $7.4 billion) (~1979)

10 Unireg Begins Essentially, the origin of what we know MySQL as today, establishing its code base MySQL Goes Open The MySQL platform goes Open Source, and begins to follow the terms of the GPL MariaDB is founded As Oracle begins drifting further away from open source, Monty founds MariaDB designed as a pluggable replacement. MySQL is released In 1995, MySQL was first released for usage under dual licensing. Sun Acquires MySQL Sun Microsystems purchases MySQL AB for $1 billion (only to be acquired by Oracle in 2009 for $7.4 billion) 1981 (~1979)

11 Unireg Begins Essentially, the origin of what we know MySQL as today, establishing its code base MySQL Goes Open The MySQL platform goes Open Source, and begins to follow the terms of the GPL MariaDB is founded As Oracle begins drifting further away from open source, Monty founds MariaDB designed as a pluggable replacement MySQL is released Sun Acquires MySQL cpanel-supported 1981 In 1995, MySQL was first released for usage under dual licensing Sun Microsystems purchases MySQL AB for $1 billion (only to be acquired by Oracle in 2009 for $7.4 billion) 2009 In response to industry shifts indicating a move towards MariaDB, cpanel officially introduced support for it into the release. (~1979)

12 Unireg Begins Essentially, the origin of what we know MySQL as today, establishing its code base MySQL Goes Open The MySQL platform goes Open Source, and begins to follow the terms of the GPL MariaDB is founded As Oracle begins drifting further away from open source, Monty founds MariaDB designed as a pluggable replacement The battle continues While MariaDB made major progress for the industry, MySQL 5.7 and 8.0 have brought new drive to the competition. MySQL is released Sun Acquires MySQL cpanel-supported 1981 (~1979) In 1995, MySQL was first released for usage under dual licensing Sun Microsystems purchases MySQL AB for $1 billion (only to be acquired by Oracle in 2009 for $7.4 billion) 2009 In response to industry shifts indicating a move towards MariaDB, cpanel officially introduced support for it into the release. Now & Later

13 WHAT S THE DIFFERENCE?

14 MySQL 5.7 MARIADB 10.2 JSON DATATYPE JSON DATATYPE (KIND ENGINE IMPROVEMENTS ENGINE IMPROVEMENTS SECURITY IMPROVEMENTS SECURITY IMPROVEMENTS ADDED SYNTAX/QUERIES ADDED SYNTAX/QUERIES

15 MySQL 5.7 MARIADB 10.2 JSON DATATYPE JSON DATATYPE (KIND Stores data in binary Stores data as LONGTEXT SELECT JSON_EXTRACT(c, $.id ) 25 JSON functions 26 JSON functions SELECT c->"$.id" JSON_PRETTY JSON_STORAGE_ JSON_COMPAC JSON_DETAILE JSON_MERGE_PATC JSON_MERGE_PRE JSON_EXISTS JSON_LOOSE -> ->> JSON_QUERY JSON_VALUE JSON_EXTRACT JSON_UNQUOTE(JSON_EX

16 MySQL 5.7 MARIADB 10.2 ENGINE IMPROVEMENTS ENGINE IMPROVEMENTS mysql> SHOW STATUS WHERE Variable_name='InnoDB_buffer_pool_resize_status'; DDL Performance InnoDB Variable_name Value Dynamic Buffer Pool Smart Doublewrite Innodb_buffer_pool_resize_status Resizing also other hash tables More Transportable MyISAM

17 MySQL 5.7 MARIADB 10.2 ENGINE IMPROVEMENTS ENGINE IMPROVEMENTS InnoDB InnoDB DDL Performance Smart Doublewrite InnoDB as Default Dynamic Buffer Pool More Transportable Spatial Indexes Improved Crash Recovery MyISAM

18 MySQL 5.7 MARIADB 10.2 key_cache_segments ENGINE IMPROVEMENTS ENGINE IMPROVEMENTS Description: The number of segments in a key cache. InnoDB Commandline: --key-cache-segments=# InnoDB DDL Performance Scope: Global Smart Doublewrite InnoDB as Default Dynamic: Yes Dynamic Buffer Pool More Transportable Spatial Indexes Improved Crash Recovery Type: numeric MyISAM Default Value: 0 (non-segmented) Range: 0 to 64 MyISAM Segmented Key Caching Adjustable Hash Size

19 MySQL 5.7 MARIADB 10.2 ENGINE IMPROVEMENTS ENGINE IMPROVEMENTS mysql> SHOW STATUS WHERE Variable_name='InnoDB_buffer_pool_resize_status'; Variable_name Value DDL Performance InnoDB Innodb_buffer_pool_resize_status Resizing also other hash tables Dynamic Buffer Pool Smart Doublewrite More Transportable InnoDB MyISAM MyRocks MyISAM Aria CONNECT MongoDB

20 MySQL 5.7 MARIADB 10.2 SECURITY IMPROVEMENTS Command-Line Format SECURITY IMPROVEMENTS --require-secure-transport[={off ON}] Secure by Default Introduced: Single Root System Variable: require_secure_transport Require Secure Transport Scope: Global Dynamic: Yes User table constraints Type: Boolean Default Value: OFF

21 MySQL 5.7 MARIADB 10.2 SECURITY IMPROVEMENTS Command-Line Format SECURITY IMPROVEMENTS --require-secure-transport[={off ON}] Secure by Default ed25519 Introduced: Single Root System Require Secure Variable: require_secure_transport Transport Scope: Global OpenSSL 1.1 & LibreSSL Dynamic: Yes User table constraints Type: Boolean AWS Key Management Default Value: OFF

22 MySQL 5.7 MARIADB 10.2 ADDED SYNTAX/QUERIES ADDED SYNTAX/QUERIES EXPLAIN MySQL [(none)]> explain for connection 1; id select_type table type possible_keys key key_len ref rows Extra SIMPLE orders ALL NULL NULL NULL NULL Using where No Temp Tables on UNION ALL

23 MySQL 5.7 MARIADB 10.2 ADDED SYNTAX/QUERIES SHOW CREATE USER ADDED SYNTAX/QUERIES *************************** 1. row *************************** EXPLAIN CREATE USER SHOW CREATE USER REQUIRE ISSUER 'foo_issuer' No Temp Tables on UNION ALL SUBJECT 'foo_subject' CHECK CONSTRAINT CIPHER 'text' FOLLOWS/PRECEDES

24 SO WHAT S THE PUBLIC DOING?

25

26

27 DROPPING IN?

28 THE RISK OF MOVING TO MARIADB SERVER IF YOU AREN T USING NEWER MYSQL FEATURES MAY BE MINIMAL, BUT THE RISK OF MOVING OUT OF MARIADB SERVER TO MYSQL IS VERY PREVALENT. Percona

29 It depends MYSQL MARIADB ?

30 5.7 -> 10.1 Incompatibilities MariaDB 10.1 does not support MySQL 5.7's online undo tablespace truncation. However, this feature was added to MariaDB MariaDB 10.1 does not support MySQL 5.7's transportable tablespaces for partitioned InnoDB tables. ALTER TABLE... {DISCARD IMPORT} PARTITION is not supported. MariaDB 10.1 does not support the use of multiple triggers of the same type for a table. This feature was introduced in MariaDB

31 5.7 -> 10.2 Incompatibilities MariaDB 10.2 does not support MySQL's SELECT MAX_STATEMENT_TIME = N... syntax MariaDB 10.2 does not support MySQL 5.7's native InnoDB partitioning handler. MariaDB 10.2 does not support the MySQL X plugin. MariaDB 10.2 does not support the MySQL Memcached plugin. Users created with MySQL's SHA256 password algorithm cannot be used in MariaDB MariaDB's GTID is not compatible with MySQL's.

32 mysql> SHOW STATUS WHERE Variable_name='InnoDB_buffer_pool_resize_status'; Variable_name Value Innodb_buffer_pool_resize_status Resizing also other hash tables

33 What d you think? events.bizzabo.com/polls/ Rate this presentation on the Conference app or by navigating to the above link in your browser.

34 Or, without the app: events.bizzabo.com/polls/011721