Innovate faster and cut risk with PHP experts from Zend Services.
Beginning to advanced PHP classes to learn and earn global certification.
Help me choose >
Submit support requests and browse self-service resources.
Even though new PHP releases include improved security provisions and an exciting mix of new features, many developers dread PHP upgrades. And, with PHP versions only community supported for three years, teams need to upgrade frequently -- or face the reality of deploying unsupported PHP.
In this blog, we look at some of the key challenges teams face when upgrading PHP, including notes on the benefits of upgrading, planning PHP upgrades, and how to make the process as streamlined as possible.
Typically, the biggest challenges people face with a PHP migration relate to justification and planning. It’s not unusual for PHP applications to have several million lines of code. And the scope of manually migrating applications to a new release can be ominous, especially when it comes to developers’ schedules. That’s because:
Most new releases double application performance. Looking back at a historic example, PHP 7.3 performance jumps 2X to 3X of applications running PHP 5.
These performance gains can translate into faster response times for users and improved service levels. In addition, application performance gains can sometimes make significant hardware consolidation possible, which can result in thousands of dollars in monthly savings.
Given the fast lifecycle for PHP version releases, teams are tasked with upgrading / migrating to the latest version of PHP more frequently than ever before. For more information on the latest PHP versions, be sure to check out our resource collection Exploring PHP Versions: Performance, Security, and Feature Comparisons. It includes blogs, white papers, and webinars that discuss various PHP versions and the benefits they can bring to your organization.
Visit the PHP Version Hub >>
A PHP upgrade will help:
There are two things I always stress when it comes to planning PHP upgrades:
Planning Your Next PHP Upgrade or Migration?This white paper details the best practices teams need to consider when planning and executing PHP migrations and upgrades.Download Free Copy
This white paper details the best practices teams need to consider when planning and executing PHP migrations and upgrades.
Download Free Copy
Yes, you need to test your apps — even if your resources are spread thin. Corporate web applications support customers. To ensure every single person has a seamless, reliable experience, you need to test.
Testing becomes more feasible if you do it as you make changes. Waiting to run all your tests until you are done with your code migration will make it much more difficult and time-consuming to pinpoint issues and their causes.
I recommend making one change, and then testing it. Repeat this cycle until the migration is complete. In one day, our developers typically make and test 10 to 14 small changes.
Many companies engage Zend PHP Migration Services for help with PHP upgrades. Why? Our PHP consultants:
See Available Migration Services