mysql为什么直接8.0_为什么要迁移到MySQL8.0？

原标题：为什么要迁移到MySQL8.0？

来自公众号：老叶茶馆，作者：lefred，翻译：徐晨亮

原文链接：https://lefred.be/content/replace-mariadb-10-3-by-mysql-8-0/

本文建议横屏阅读，效果更佳(本文涉及到的链接见文章最后)

MySQL 8.0 brings a lot of new features. These features make MySQL database much more secure (like new authentication, secure password policies and management, …) and fault tolerant (new data dictionary), more powerful (new redo log design, less contention, extreme scale out of InnoDB, …), better operation management (SQL Roles, instant add columns), many (but really many!) replication enhancements and native group replication… and finally many cool stuff like the new Document Store, the new MySQL Shell and MySQL InnoDB Cluster that you should already know if you follow this blog (see theseTOP 10 for features for developersand thisTOP 10 for DBAs & OPS).

MySQL8.0带来了很多新特性。这些新特性使得MySQL数据库更加安全(例如新的认证方式，安全的密码策略和管理方式，...)和容错(新的数据字典)功能更强大(新的redo设计，争用更少，极度扩展InnoDB，…)，更好的操作管理(SQL角色，即时添加列 )，很多(其实真的很多)复制增强和本地组复制...最后还有很多很酷的东西例如文档存储，全新的MySQL Shell和MySQL InnoDB cluster，如果你看过以下这些博客的话你应该已经知TOP 10 for features for developers道了(TOP 10 for features for developers和TOP 10 for DBAs & OPS)

不再是替代者

We saw in this previous post how to migrate from MariaDB 5.5 (default on CentOS/RedHat 7) to MySQL. This was a straight forward migration as at the time MariaDB was a drop in replacement for MySQL…but this is not the case anymore since MariaDB 10.x !

我们在上一篇文章中看到了如何从MariaDB 5.5(在CentOS/RedHat7上默认)迁移到MySQL。这是一个直接的迁移，因为当时MariDB是MySQL的替代者…但是从MariaDB 10.x开始情况就不一样了。

让我们开始迁移到MySQL8.0

选项

Two possibilities are available to us:

Use logical dump for schemes and data

Use logical dump for schemes and transportable InnoDB tablespaces for the data

我们有两种方式：

对schema和数据逻辑导出

对schema逻辑导出，使用InnoDB表空间传输