We met with Vinicius Grippa, a Senior Support Engineer at Percona. He is also active in the open source community and was recognized as a MySQL Rock Star in 2023.
In the previous interview with Vinicius, we discussed the upcoming End of Life (EOL) for MySQL 5.7. Now that MySQL 5.7 has reached EOL, MySQL 8 is the new version. We are discussing what this change means.
Let’s explore how users adapt to MySQL 8 and how Percona is helping with this transition.
We compiled a series of questions from various users and answered them with Vinicius. You can watch the full videos here.
Let’s start:
What is your top strategy advice for users still using the EOL MySQL version?
Grippa emphasizes that the best practices for upgrading remain unchanged, like testing and having backups, which are common in upgrading versions.
Oracle changed the release model, categorizing versions into Innovation and Stable releases, which is crucial for users. MySQL 8.0 versions are considered Stable, focusing on bug fixes and security improvements, with new features introduced in Innovation releases. This change aims to make migrations smoother and less disruptive for databases and applications.
Some 5.7 users seem to have a ‘If it is not broken, don’t touch it.” How will this hurt them in the long term?
Staying on an unsupported version poses long-term security risks and may not meet compliance requirements for specific industries. While MySQL 5.7 may suffice for databases behind a VPN and not exposed to the internet, upgrading to a supported version is crucial for security and compliance.
MySQL 8 offers more stability, features, and the convenience of performing specific tasks online, enhancing everyday operations without disrupting business. Percona supports migration through extended end-of-life support, forums, and blog discussions, highlighting the significant user base transitioning to managed database services with cloud providers, which may eventually force migration to MySQL 8.
Security and performance implications of staying on an EOL version versus upgrading to the latest Percona Server for MySQL.
Upgrading from an old version to the latest Percona Server for MySQL is crucial for addressing compliance issues, especially under the strict data security regulations in Europe and the United States.
Staying updated helps prevent data leaks and security breaches. Technically, newer versions like MySQL 8 offer enhanced features that simplify database management tasks, such as online modifications without restarts, making life easier for DBAs. With cloud providers moving away from MySQL 5.7, planning for migration is essential for continued support and performance improvements.
How does Percona specifically support users through this transition, especially those facing complex upgrade scenarios?
Percona offers comprehensive support for users navigating complex MySQL upgrades, providing three primary services: expert support for teams seeking specialist coverage, managed services for those opting for entire delegation, and consultancy for hands-on maintenance guidance.
Besides these paid services, Percona actively supports the community through informative blog posts by engineers on various upgrade scenarios, shared experiences to prevent common errors, and a forum for troubleshooting and peer advice.
Percona offers several support options for migrating users or considering migrating to the latest MySQL version.
What is Percona Everest? And why is Kubernetes involved in this?
Percona’s latest product, Percona Everest, is now in beta, and its primary goal is simplifying database management, especially for startups or teams without dedicated DBAs.
Percona Everest empowers businesses to focus more on strategic objectives rather than technical details by automating deployment, maintenance, backups, and monitoring. Percona Everest is designed to integrate with Kubernetes, offering a simplified interface for deploying instances with high availability, backups, and monitoring. Percona encourages user feedback to enhance Everest further, highlighting its commitment to easy use and flexibility to avoid vendor lock-in.
Image01: Architecture of Percona Everest
What are the key achievements or contributions for being recognized as a MySQL Rock Star 202?
Vinicius Grippa, awarded as a MySQL Rockstar 2023, highlights his contributions that led to this recognition. He shared the importance of sharing knowledge through blog posts, reporting bugs to enhance MySQL and Percona’s functionality, and organizing conferences and community engagement.
The work of Vinicius exemplifies the collaborative spirit of the open-source community. It also encourages active participation and knowledge sharing among members. Everyone’s perspective is valuable, underscoring the community’s openness to contributions from developers and non-developers alike, which Vinicius highlights from being part of a community.
What’s next:
To learn more about upgrading from EOL MySQL versions and Percona’s support, check this blog post, Considering Alternatives for Your MySQL Migration. Why Percona Should Be Your First Choice
Are you curious about Percona Everest? You can also visit the Percona Everest Website.
Remember to join community forums if you have any questions about our software.
Not ready to give up MySQL 5.7? Keep MySQL 5.7 secure and performant with post-EOL support.
Get MySQL 5.7 post-EOL support
