Tweet
Tweet

Slide 1

Slide 1 text

Frédéric Descamps Community Manager Oracle MySQL Confoo.CA - February 2024 The Evolution of a MySQL Database Architecture from single instance to mutli-regions DR with read replicas and transparent read/write spli ing

Slide 2

Slide 2 text

The Journey To MySQL InnoDB ClusterSet Copyright @ 2024 Oracle and/or its affiliates. 2

Slide 3

Slide 3 text

Who am I ? about.me/lefred Copyright @ 2024 Oracle and/or its affiliates. 3

Slide 4

Slide 4 text

@lefred MySQL Evangelist using MySQL since version 3.20 devops believer likes living in h ps://lefred.be Frédéric Descamps Copyright @ 2024 Oracle and/or its affiliates. 4

Slide 5

Slide 5 text

Best Practices in 2024 con guration parameters Copyright @ 2024 Oracle and/or its affiliates. 5

Slide 6

Slide 6 text

During this presentation I assume that... your system is MySQL 8.0.36 or more recent (Innovation Release 8.3.0) you are using only InnoDB you have the binary logs enabled the binary log format is ROW you are using GTIDs Copyright @ 2024 Oracle and/or its affiliates. 6

Slide 7

Slide 7 text

Evolution to High Availability MySQL 8.x Copyright @ 2024 Oracle and/or its affiliates. 7

Slide 8

Slide 8 text

Copyright @ 2024 Oracle and/or its affiliates. 8

Slide 9

Slide 9 text

This is where it all begins... reminder: we ONLY use InnoDB we keep the default durability se ings One single MySQL instance Copyright @ 2024 Oracle and/or its affiliates. 9

Slide 10

Slide 10 text

One single MySQL instance Copyright @ 2024 Oracle and/or its affiliates. / / RPO ? ? RTO 10

Slide 11

Slide 11 text

Next Level (level up) The database becomes more important, loosing it might be an issue... Copyright @ 2024 Oracle and/or its affiliates. 11

Slide 12

Slide 12 text

Next Level (level up) The database becomes more important, loosing it might be an issue... RTO → hours Copyright @ 2024 Oracle and/or its affiliates. 11

Slide 13

Slide 13 text

Next Level (level up) The database becomes more important, loosing it might be an issue... RTO → hours RPO → 1 day Copyright @ 2024 Oracle and/or its affiliates. 11

Slide 14

Slide 14 text

Next Level (level up) The database becomes more important, loosing it might be an issue... RTO → hours RPO → 1 day RTO: Recovery Time Objective (how long to recover) RPO: Recovery Point Objective (how much data can be lost) Copyright @ 2024 Oracle and/or its affiliates. 11

Slide 15

Slide 15 text

Physical Backups Logical Backups For logical backups, please use MySQL Shell Dump & Load Utility ! Backups Copyright @ 2024 Oracle and/or its affiliates. 12

Slide 16

Slide 16 text

One single MySQL instance with daily backups Copyright @ 2024 Oracle and/or its affiliates. hours 1 day RPO ? ? RTO 13

Slide 17

Slide 17 text

Next Level (level up) 1 day RPO ? Really ?? We want to reduce it to minutes at least ! Copyright @ 2024 Oracle and/or its affiliates. 14

Slide 18

Slide 18 text

Next Level (level up) 1 day RPO ? Really ?? We want to reduce it to minutes at least ! RTO → hours Copyright @ 2024 Oracle and/or its affiliates. 14

Slide 19

Slide 19 text

Next Level (level up) 1 day RPO ? Really ?? We want to reduce it to minutes at least ! RTO → hours RPO → minutes Copyright @ 2024 Oracle and/or its affiliates. 14

Slide 20

Slide 20 text

These are the defaults in MySQL 8.0: Durable Binlogs We enable binary logs allowing to replay the modi cations since the last backup: Copyright @ 2024 Oracle and/or its affiliates. 15

Slide 21

Slide 21 text

One single MySQL instance with daily backups and binlogs Copyright @ 2024 Oracle and/or its affiliates. hours minutes RPO ? ? RTO 16

Slide 22

Slide 22 text

Point-in-Time Recovery (PITR) PITR is the technique by which an administrator can restore or recover a data set to a certain point in the past. With MySQL, point-in-time recovery involves restoring a dump of the data and then replaying the binlogs from and to a speci c point. This technique is used to: solve an issue perform a live migration Copyright @ 2024 Oracle and/or its affiliates. 17

Slide 23

Slide 23 text

Point-in-Time Recovery : how does it work ? day 1 BACKUPS Binlogs day 2 day 3 day 4 .001 .002 .003 .004 .005 .006 .007 .008 .009 .010 Copyright @ 2024 Oracle and/or its affiliates. 18

Slide 24

Slide 24 text

Point-in-Time Recovery : how does it work ? day 1 BACKUPS Binlogs day 2 we want to recover up to this point day 3 day 4 .001 .002 .003 .004 .005 .006 .007 .008 .009 .010 Copyright @ 2024 Oracle and/or its affiliates. 19

Slide 25

Slide 25 text

Point-in-Time Recovery : how does it work ? day 1 BACKUPS Binlogs day 2 we want to recover up to this point day 3 day 4 .001 .002 .003 .004 .005 .006 .007 .008 .009 .010 1. we restore the dump of day 3 Copyright @ 2024 Oracle and/or its affiliates. 20

Slide 26

Slide 26 text

Point-in-Time Recovery : how does it work ? day 1 BACKUPS Binlogs day 2 day 3 day 4 .001 .002 .003 .004 .005 .006 .007 .008 .009 .010 2. we replay the binlog (.008) 1. we restore the du,p of day 3 Copyright @ 2024 Oracle and/or its affiliates. 21

Slide 27

Slide 27 text

Point-in-Time Recovery : important concepts Usually, after a backup (and its veri cation), the binary log les are purged from the MySQL server: Copyright @ 2024 Oracle and/or its affiliates. 22

Slide 28

Slide 28 text

Point-in-Time Recovery : important concepts Usually, after a backup (and its veri cation), the binary log les are purged from the MySQL server: Copyright @ 2024 Oracle and/or its affiliates. day 1 BACKUPS Binlogs day 2 day 3 day 4 .001 .002 .003 .004 .005 .006 .007 .008 .009 .010 22

Slide 29

Slide 29 text

Point-in-Time Recovery : important concepts Usually, after a backup (and its veri cation), the binary log les are purged from the MySQL server: Copyright @ 2024 Oracle and/or its affiliates. day 1 BACKUPS Binlogs day 2 day 3 day 4 .001 .002 .003 .004 .005 .006 .007 .008 .009 .010 day 1 BACKUPS pontential recovery points Binlogs day 2 day 3 day 4 .001 .002 .003 .004 .005 .006 .007 .008 .009 .010 } 22

Slide 30

Slide 30 text

Next Level (level up) My data is very important and I've a heavy workload... I would like to loose less than a second in case of a problem ! Copyright @ 2024 Oracle and/or its affiliates. 23

Slide 31

Slide 31 text

Next Level (level up) My data is very important and I've a heavy workload... I would like to loose less than a second in case of a problem ! RTO → hours Copyright @ 2024 Oracle and/or its affiliates. 23

Slide 32

Slide 32 text

Next Level (level up) My data is very important and I've a heavy workload... I would like to loose less than a second in case of a problem ! RTO → hours RPO → less than a second Copyright @ 2024 Oracle and/or its affiliates. 23

Slide 33

Slide 33 text

Enable GTIDs (they should be already !) Save in realtime the binary logs to a di erent system (OCI Object Storage, S3, ...) VCN 10.0.0.0/16 Public Subnet 10.0.0.0/24 Private Subnet 10.0.1.0/24 MySQL Shell MySQL Database Service Internet Gateway Oracle Cloud Infrastructure Availability Domain 1 Fault Domain 1 mysql-dump-bucket mysql-binlogs-bucket Object Storage dump instance stream binlogs Improved Point-in-Time Recovery (PITR) Copyright @ 2024 Oracle and/or its affiliates. 24

Slide 34

Slide 34 text

with MySQL restart Enabling GTIDs Copyright @ 2024 Oracle and/or its affiliates. 25

Slide 35

Slide 35 text

with MySQL restart without MySQL restart Enabling GTIDs Copyright @ 2024 Oracle and/or its affiliates. 25

Slide 36

Slide 36 text

Saving Binlogs Copyright @ 2024 Oracle and/or its affiliates. 26

Slide 37

Slide 37 text

Saving Binlogs On another system: mysqlbinlog --raw --read-from-remote-server --stop-never --host 10.0.0.2 \ --port 3306 -u getbinlog -ppassword \ --ssl-mode='REQUIRED' binlog.xxxxxx Copyright @ 2024 Oracle and/or its affiliates. 26

Slide 38

Slide 38 text

Point-in-Time Recovery : important concepts (2) As you may have noticed, we can only recover at the exact time of the backups and we can only do a one-o recovery from the last one! This is why it is recommended to relocate/o oad the binlogs (to another server, a NAS, the cloud, ...). This will allow for a point-in-time recovery at any moment in time: Copyright @ 2024 Oracle and/or its affiliates. 27

Slide 39

Slide 39 text

Point-in-Time Recovery : important concepts (2) As you may have noticed, we can only recover at the exact time of the backups and we can only do a one-o recovery from the last one! This is why it is recommended to relocate/o oad the binlogs (to another server, a NAS, the cloud, ...). This will allow for a point-in-time recovery at any moment in time: Copyright @ 2024 Oracle and/or its affiliates. } day 1 BACKUPS Binlogs day 2 day 3 day 4 .001 .002 .003 .004 .005 .001 .002 .003 .004 .005 .006 .007 .008 .009 .010 .006 .007 .008 .009 .010 binlog streaming possible recovery points 27

Slide 40

Slide 40 text

One single MySQL instance with daily backups and external binlogs archiving Copyright @ 2024 Oracle and/or its affiliates. hours < 1 second RPO ? ? RTO 28

Slide 41

Slide 41 text

Next Level (level up) My service is now very important, I would like my database to be available again within minutes in case of an incident. Copyright @ 2024 Oracle and/or its affiliates. 29

Slide 42

Slide 42 text

Next Level (level up) My service is now very important, I would like my database to be available again within minutes in case of an incident. RTO → minutes Copyright @ 2024 Oracle and/or its affiliates. 29

Slide 43

Slide 43 text

Next Level (level up) My service is now very important, I would like my database to be available again within minutes in case of an incident. RTO → minutes RPO → less than a second Copyright @ 2024 Oracle and/or its affiliates. 29

Slide 44

Slide 44 text

Based on the well known Asynchronous Replication But easier... easier is always be er ! Data provisioning included (clone) 2 or more nodes Manual Failover Transparent/Automatic query routing with MySQL Router MySQL InnoDB ReplicaSet Copyright @ 2024 Oracle and/or its affiliates. 30

Slide 45

Slide 45 text

MySQL InnoDB ReplicaSet Copyright @ 2024 Oracle and/or its affiliates. 31

Slide 46

Slide 46 text

MySQL InnoDB ReplicaSet Connected to the actual server (our single instance): JS > dba.configureReplicaSetInstance() JS > rs=dba.createReplicaSet('myreplicaset') On the new extra server where only MySQL is installed (server and shell): JS > dba.configureReplicaSetInstance() And again on the main instance (our single instance): JS > rs.addInstance('mysql-2') Copyright @ 2024 Oracle and/or its affiliates. 32

Slide 47

Slide 47 text

MySQL InnoDB ReplicaSet - examples Copyright @ 2024 Oracle and/or its affiliates. 33

Slide 48

Slide 48 text

MySQL InnoDB ReplicaSet - examples Copyright @ 2024 Oracle and/or its affiliates. 34

Slide 49

Slide 49 text

MySQL InnoDB ReplicaSet - examples Copyright @ 2024 Oracle and/or its affiliates. 35

Slide 50

Slide 50 text

MySQL Router MySQL Router is very easy to con gure, you only need to use the bootstrap command ! Copyright @ 2024 Oracle and/or its affiliates. 36

Slide 51

Slide 51 text

MySQL Router As usual, this is also visible in MySQL Shell Copyright @ 2024 Oracle and/or its affiliates. 37

Slide 52

Slide 52 text

MySQL InnoDB ReplicaSet - Manual Failover Copyright @ 2024 Oracle and/or its affiliates. MySQL Shell is connected to MySQL InnoDB ReplicaSet via MySQL Router. 38

Slide 53

Slide 53 text

MySQL InnoDB ReplicaSet - Manual Failover Copyright @ 2024 Oracle and/or its affiliates. 39

Slide 54

Slide 54 text

MySQL RelicaSet Copyright @ 2024 Oracle and/or its affiliates. minutes < 1 second RPO ? ? RTO rto > 40

Slide 55

Slide 55 text

Next Level (level up) My service is very important, I'd like to be operational almost all the time (automatic failover) and never lose any data! Copyright @ 2024 Oracle and/or its affiliates. 41

Slide 56

Slide 56 text

Next Level (level up) My service is very important, I'd like to be operational almost all the time (automatic failover) and never lose any data! RTO → seconds Copyright @ 2024 Oracle and/or its affiliates. 41

Slide 57

Slide 57 text

Next Level (level up) My service is very important, I'd like to be operational almost all the time (automatic failover) and never lose any data! RTO → seconds RPO → 0 Copyright @ 2024 Oracle and/or its affiliates. 41

Slide 58

Slide 58 text

Based on native Group Replication But easier.... easier is always be er ! Data provisioning included (clone) 3 or more nodes (odd number) Automatic Failover Uses MySQL Router Con gurable Consistency Levels MySQL InnoDB Cluster Copyright @ 2024 Oracle and/or its affiliates. 42

Slide 59

Slide 59 text

MySQL InnoDB Cluster Copyright @ 2024 Oracle and/or its affiliates. 43

Slide 60

Slide 60 text

On the ReplicaSet's Primary Instance: JS > rs=dba.getReplicaSet() JS > rs.dissolve() JS > cluster=dba.createCluster('myCluster') JS > cluster.addInstance('mysql-2') MySQL InnoDB Cluster Copyright @ 2024 Oracle and/or its affiliates. 44

Slide 61

Slide 61 text

On the ReplicaSet's Primary Instance: JS > rs=dba.getReplicaSet() JS > rs.dissolve() JS > cluster=dba.createCluster('myCluster') JS > cluster.addInstance('mysql-2') JS > dba.configureInstance() From any member of the cluster: JS > cluster=dba.getCluster() JS > cluster.addInstance('mysql-3') Finally, we can con gure MySQL Router again: # mysqlrouter --bootstrap \ clusteradmin@single-mysql:3306 \ --conf-use-gr-notifications \ --user mysqlrouter --force # systemctl restart mysqlrouter MySQL InnoDB Cluster We can now add a third instance to bene t from the automatic failover: Copyright @ 2024 Oracle and/or its affiliates. 44

Slide 62

Slide 62 text

MySQL InnoDB Cluster Copyright @ 2024 Oracle and/or its affiliates. 45

Slide 63

Slide 63 text

MySQL InnoDB Cluster Copyright @ 2024 Oracle and/or its affiliates. seconds 0 RPO ? ? RTO rto > 46

Slide 64

Slide 64 text

MySQL InnoDB Cluster: consistency levels MySQL InnoDB Cluster operates, by default, in single-primary mode: Apps and users write to the primary instance What guarantees do we have that: We always read the most up-to-date data? We do not read stale data of an evicted server? Dirty reads do not happen? Copyright @ 2024 Oracle and/or its affiliates. 47

Slide 65

Slide 65 text

mysql> show variables like 'group_replication_consistency'; +-------------------------------+----------+ | Variable_name | Value | +-------------------------------+----------+ | group_replication_consistency | EVENTUAL | +-------------------------------+----------+ MySQL InnoDB Cluster: consistency levels The default consistency level is EVENTUAL. This means that there is no synchronization point for the transactions, when you perform a write on a node, if you immediately read the same data on another node, it is eventually there. Copyright @ 2024 Oracle and/or its affiliates. 48

Slide 66

Slide 66 text

mysql> show variables like 'group_replication_consistency'; +-------------------------------+----------+ | Variable_name | Value | +-------------------------------+----------+ | group_replication_consistency | EVENTUAL | +-------------------------------+----------+ MySQL InnoDB Cluster: consistency levels The default consistency level is EVENTUAL. This means that there is no synchronization point for the transactions, when you perform a write on a node, if you immediately read the same data on another node, it is eventually there. Since MySQL 8.0.16, we have the possibility to set the synchronization point at read or at write or both (globally or for a session). Copyright @ 2024 Oracle and/or its affiliates. 48

Slide 67

Slide 67 text

Consistency: BEFORE (READ) Copyright @ 2024 Oracle and/or its affiliates. As a DBA, I want to load balance my reads without deploying additional restrictions on which server I read from to avoid reading stale data, my group writes are much more than my group reads. 49

Slide 68

Slide 68 text

Consistency: BEFORE (READ) < > Copyright @ 2024 Oracle and/or its affiliates. As a DBA, I want to load balance my reads without deploying additional restrictions on which server I read from to avoid reading stale data, my group writes are much more than my group reads. As a developer, I want specific transactions in my workload to always read up- to-date data from the group, so that whenever that sensitive data is updated, I will enforce that reads shall read the most up to date value. 49

Slide 69

Slide 69 text

Consistency: BEFORE (READ) Copyright @ 2024 Oracle and/or its affiliates. 50

Slide 70

Slide 70 text

Consistency: AFTER (WRITE) Copyright @ 2024 Oracle and/or its affiliates. I want to load balance my reads without deploying additional restrictions on which server I read from to avoid reading stale data, my group writes are much less than my group reads. 51

Slide 71

Slide 71 text

Consistency: AFTER (WRITE) < > Copyright @ 2024 Oracle and/or its affiliates. I want to load balance my reads without deploying additional restrictions on which server I read from to avoid reading stale data, my group writes are much less than my group reads. I have a group that mostly does reads-only, I want my read-write transactions to be applied everywhere once they commit, so that subsequent reads are done on up-to-date data that includes my latest write. Without paying at reads. 51

Slide 72

Slide 72 text

Consistency: AFTER (WRITE) Copyright @ 2024 Oracle and/or its affiliates. 52

Slide 73

Slide 73 text

Consistency: BEFORE_AND_AFTER < > Copyright @ 2024 Oracle and/or its affiliates. I want that my application to replicate data as close as possible to synchronous. And of course I'm OK to pay the required price ! 53

Slide 74

Slide 74 text

Consistency: BEFORE_AND_AFTER It's also possible and recommended for the most restrictive levels to de ne it at statement session level: Copyright @ 2024 Oracle and/or its affiliates. 54

Slide 75

Slide 75 text

Next Level (level up) And if something happens to our data center ?? Copyright @ 2024 Oracle and/or its affiliates. 55

Slide 76

Slide 76 text

Next Level (level up) And if something happens to our data center ?? How can we deploy a Disaster Recovery solution ? Copyright @ 2024 Oracle and/or its affiliates. 55

Slide 77

Slide 77 text

Next Level (level up) And if something happens to our data center ?? How can we deploy a Disaster Recovery solution ? Copyright @ 2024 Oracle and/or its affiliates. MySQL InnoDB ClusterSet !! 55

Slide 78

Slide 78 text

The Disaster Recovery Evolution ! available since MySQL 8.0.27 fencing support since 8.0.28 MySQL InnoDB ClusterSet Copyright @ 2024 Oracle and/or its affiliates. 56

Slide 79

Slide 79 text

The result of several transformations during previous releases: 8.0.22: Automatic Connection Failover (Async Replication Channels) 8.0.23: Automatic Connection Failover (Async Replication Channels using Group Replication) 8.0.24: transformation of skip-replica-start en global, persistent and read-only variable 8.0.26: Actions added for Group Replication's members (ex: super_read_only con gurable) 8.0.26: Speci c UUID added for structural events change of the Group (View_change_log_event) 8.0.27: Asynchronous Replication Channel automatically follows the Primary. Copyright @ 2024 Oracle and/or its affiliates. 57

Slide 80

Slide 80 text

MySQL InnoDB ClusterSet Copyright @ 2024 Oracle and/or its affiliates. 58

Slide 81

Slide 81 text

MySQL InnoDB ClusterSet Copyright @ 2024 Oracle and/or its affiliates. More complex architectures can be deployed ! 58

Slide 82

Slide 82 text

MySQL InnoDB ClusterSet Copyright @ 2024 Oracle and/or its affiliates. More complex architectures can be deployed ! 58

Slide 83

Slide 83 text

On the Cluster's Primary Instance: JS > cluster=dba.getCluster() JS > cs=cluster.createClusterSet('mydomain') We can already check the status: JS > cs.status() Now let's create the Replica Cluster: JS > cluster2=cs.createReplicaCluster( 'dc2-mysql-4', 'mycluster2') MySQL InnoDB ClusterSet Copyright @ 2024 Oracle and/or its affiliates. 59

Slide 84

Slide 84 text

On the Cluster's Primary Instance: JS > cluster=dba.getCluster() JS > cs=cluster.createClusterSet('mydomain') We can already check the status: JS > cs.status() Now let's create the Replica Cluster: JS > cluster2=cs.createReplicaCluster( 'dc2-mysql-4', 'mycluster2') And we add the other 2 instances: JS > cluster2.addInstance( 'dc2-mysql-5') JS > cluster2.addInstance( 'dc2-mysql-6') Finally, we need to bootstrap another time MySQL Router: # mysqlrouter --bootstrap \ clusteradmin@single-mysql:3306 \ --conf-use-gr-notifications \ --user mysqlrouter --force # systemctl restart mysqlrouter MySQL InnoDB ClusterSet Copyright @ 2024 Oracle and/or its affiliates. 59

Slide 85

Slide 85 text

MySQL InnoDB ClusterSet Copyright @ 2024 Oracle and/or its affiliates. seconds 0 RPO ? ? RTO possible rpo>0 rto > 60

Slide 86

Slide 86 text

Extra Since MySQL 8.0.19, the connectors also support dns-srv which, together with a discovery service such as Consul, can replace MySQL Router when it is impossible to install it on the application servers: Copyright @ 2024 Oracle and/or its affiliates. 61

Slide 87

Slide 87 text

Extra Since MySQL 8.0.19, the connectors also support dns-srv which, together with a discovery service such as Consul, can replace MySQL Router when it is impossible to install it on the application servers: Copyright @ 2024 Oracle and/or its affiliates. 61

Slide 88

Slide 88 text

More with Innovation Releases Copyright @ 2024 Oracle and/or its affiliates. 62

Slide 89

Slide 89 text

Scaling Reads Evolution ! available since MySQL 8.1.0 single or multiple replicas replicate from Primary or not MySQL InnoDB Read Replicas Copyright @ 2024 Oracle and/or its affiliates. 63

Slide 90

Slide 90 text

Added support for Read Replicas with MySQL InnoDB Cluster and MySQL InnoDB ClusterSet: MySQL 8.1 - Read Replicas Copyright @ 2024 Oracle and/or its affiliates. 64

Slide 91

Slide 91 text

Read / Write Split Evolution ! available since MySQL 8.2.0 long expected feature totally transparent MySQL Transparent Read/Write Spli ing Copyright @ 2024 Oracle and/or its affiliates. 65

Slide 92

Slide 92 text

New routing policy with transparent read/write spli ing: [routing:bootstrap_rw_split] bind_address=0.0.0.0 bind_port=6450 destinations= metadata-cache://myClusterSet/?role=PRIMARY_AND_SECONDARY routing_strategy=round-robin protocol=classic connection_sharing=1 client_ssl_mode=PREFERRED server_ssl_mode=PREFERRED access_mode=auto MySQL 8.2 - Transparent Read/Write Spli ing Copyright @ 2024 Oracle and/or its affiliates. 66

Slide 93

Slide 93 text

JS > cs.listRouters() { "domainName": "myClusterSet", "routers": { "dell::system": { "hostname": "dell", "lastCheckIn": "2023-09-17 11:40:36", "roPort": "6447", "roXPort": "6449", "rwPort": "6446", "rwSplitPort": "6450", "rwXPort": "6448", "targetCluster": null, "version": "8.2.0" } } } MySQL 8.2 - Transparent Read/Write Spli ing Copyright @ 2024 Oracle and/or its affiliates. 67

Slide 94

Slide 94 text

MySQL 8.2 - Transparent Read/Write Spli ing MySQL> \c [email protected]:6450 MySQL> 127.0.0.1:6450 > select @@port, member_role from performance_schema.replication_group_members where member_id=@@server_uuid; +--------+-------------+ | @@port | member_role | +--------+-------------+ | 3330 | SECONDARY | +--------+-------------+ 1 row in set (0.0034 sec) MySQL> 127.0.0.1:6450 > start transaction; MySQL> 127.0.0.1:6450 > select @@port, member_role from performance_schema.replication_group_members where member_id=@@server_uuid; +--------+-------------+ | @@port | member_role | +--------+-------------+ | 3310 | PRIMARY | +--------+-------------+ 1 row in set (0.0016 sec) Copyright @ 2024 Oracle and/or its affiliates. 68

Slide 95

Slide 95 text

Evolution Summary Copyright @ 2024 Oracle and/or its affiliates. 69

Slide 96

Slide 96 text

Copyright @ 2024 Oracle and/or its affiliates. 70

Slide 97

Slide 97 text

Copyright @ 2024 Oracle and/or its affiliates. 71

Slide 98

Slide 98 text

Copyright @ 2024 Oracle and/or its affiliates. 72

Slide 99

Slide 99 text

Copyright @ 2024 Oracle and/or its affiliates. 73

Slide 100

Slide 100 text

Copyright @ 2024 Oracle and/or its affiliates. 74

Slide 101

Slide 101 text

Copyright @ 2024 Oracle and/or its affiliates. 75

Slide 102

Slide 102 text

Copyright @ 2024 Oracle and/or its affiliates. 76

Slide 103

Slide 103 text

Copyright @ 2024 Oracle and/or its affiliates. 77

Slide 104

Slide 104 text

Copyright @ 2024 Oracle and/or its affiliates. 78

Slide 105

Slide 105 text

MySQL Shell is now included in Visual Studio Code: Copyright @ 2024 Oracle and/or its affiliates. 79

Slide 106

Slide 106 text

Copyright @ 2024 Oracle and/or its affiliates. 80

Slide 107

Slide 107 text

Share your ❤ to MySQL #mysql #MySQLCommunity Join our slack channel! bit.ly/mysql-slack Copyright @ 2024 Oracle and/or its affiliates. 81

Slide 108

Slide 108 text

Questions ? Copyright @ 2024 Oracle and/or its affiliates. 82