![]() ![]() If you do not migrate to a modern framework, then you inevitably face each of the following consequences. You have to eventually: this is a corollary of the above point.Let’s face it, as developers we prefer to engage in projects that use current frameworks and which support modern versions of PHP (i.e., greater than or equal to 7.1). Prevent developer apathy: or, better phrased for management, retain key employees and attract more developers.Part of making the case to fellow developers and decision makers in your organization is being able to reference that Laravel is now the number one web application framework on GitHub-across all languages. The real cost is buried in day-to-day development, there’s no promised flag-day deadline to miss, and there’s no frustrating feature freeze. Migrating the smaller/simpler legacy controllers are also excellent projects for interns, student work experience or new hires getting up to speed. It also means you can migrate legacy controllers on a case-by-case basis as time and resources allow. This approach has two immediate advantages: you can develop all new features immediately on Laravel as well as use Laravel features and facades within the legacy framework. Otherwise, it hands off to the legacy framework. ![]() With the in-place migration, we add Laravel to our application so that it has the first opportunity to service a request (route). This estimate is tough to get approved by the higher-ups! Plus, have you ever met a development project that finished on time? That six months can creep to a year and even beyond very quickly. For a commercial project, it puts a real cost on the migration: ( number of developers * monthly salary * n months ) + the opportunity cost of the development freeze where n will realistically be six months at an absolute minimum. In any project, commercial or open source, this is a difficult argument to make. It means pausing all feature development and rewriting the application completely. ![]() Your gut feeling may lean towards a flag day-“let’s just get this done”-but it is the more drastic path. There are two possible approaches to migrating your application to Laravel: a flag-day or an in-place/side-by-side migration. You should also note the IXP Manager project has a single full-time developer plus me when time allows. Over the course of nine minor releases of V4, we migrated from ZF1 to Laravel finally completing the project with V4.9 released in January of 2019.Īdmittedly, a two and half year transition sounds like a long time, but this was an in-place migration where Laravel handled new and migrated controllers while anything still to be migrated fell back on ZF1. In 2015, we released V4 of IXP Manager which was a framework transition release. Zend Framework 1 went end-of-life in 2016, but its obituary was written a couple of years before that. It has run on Zend Framework V1 (ZF1) since 2008. IXP Manager is an open source tool we developed at INEX for managing IXPs (internet exchange points-network switching centers which facilitate the regional exchange of internet traffic between different networks). You can get each monthly issue in digital and print options or buy individual issues. If you'd like more articles like this one, become a subscriber today!. Download the Free Article PDF to see how it looks in the published magazine. ![]() This article was published in the March 2019 issue of php magazine. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |