Throwing Laravel into your Legacy App™
•
2 likes•1,650 views
Do you work on a legacy application and yearn for the green fields and bountiful structure of an application built on a modern framework? Do you feel like the only path to modernizing your old workhorse app is to spend months or years rewriting it from the ground up? What if you could integrate modern packages from a full stack framework at your own pace instead of having to start over from scratch? Join us as we explore using Laravel components in your Legacy App™. Modernize how your application handles configuration, routing, container, database, and much more!
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Throwing Laravel into your Legacy App™
Similar to Throwing Laravel into your Legacy App™ (20)
More from Joe Ferguson
More from Joe Ferguson (20)
Recently uploaded
Recently uploaded (20)
Throwing Laravel into your Legacy App™
- 1. Throwing Laravel into your Legacy™ Application Joe Ferguson
- 2. Who Am I? Joe Ferguson PHP Developer PHP Architect @ Ministry Brands Twitter: @JoePFerguson Organizer of @MemphisPHP @NomadPHP Lightning Talks Drone Racing Pilot
- 6. “There are no solutions, only trade offs” - Joe Ferguson - Paul M. Jones - Thomas Sowell
- 7. What is a "Legacy" application
- 8. Legacy is often used for an older production application that was written before, or without regard for modern technologies or practices.
- 9. If you ask Wikipedia… "... no-longer supported …" "... maintained by an administrator that did not develop the code …" "... supporting older file formats ..." https://en.wikipedia.org/wiki/Legacy_code
- 10. Modern Interpretation "... source code inherited from someone else …" "... source code inherited from an older version of the software ..."
- 11. Some people say… "Any code in production is not legacy” "Any code written X years ago is legacy"
- 12. Legacy is all these things As we talk about Legacy code here, we're really talking about all of these definitions
- 13. This process is not Legacy Specific…
- 14. Initial Project Overview Is there a framework? Is there a coding standard? Is there any autoloading? How are dependencies behind handled? Is there an ORM or how is the database being utilized? Is there a development environment?
- 15. Is there a framework?
- 16. Is there a coding standard?
- 17. There is a PSR for that…
- 18. How are dependencies behind handled?
- 19. Is there an ORM or how is the database being utilized?
- 20. Tools to help
- 21. PHP Coding Standards Fixer http://cs.sensiolabs.org/
- 22. PHP Coding Standards Fixer php-cs-fixer fix app --dry-run
- 24. PHP Mess Detector https://phpmd.org $ phpmd app html cleancode --reportfile report.html
- 25. Warning about Automating Code Changes
- 26. Triage Address any critical things found in Contemplation phase PHP version issues Fixing critical vulnerabilities
- 27. “We should just rewrite the app”
- 28. "This would be so much easier in framework _____________”
- 29. Why not rewrite? Progress halts entirely Business logic is rarely reused Most of the time is getting back to current functionality
- 30. Why you should refactor Progress continues Business logic reused Modernizing functionality instead of recreating
- 31. Make Decisions Build Proof of Concept(s) Ensure stakeholder buy in Avoid the allure of green fields** ** in some cases a rewrite is warranted Refactoring Approach
- 32. Existing Tests This is great! Review the tests to get an idea of coverage Passing tests become your control for any upcoming changes Confidence++
- 33. No Existing Tests Not the end of the world! Inspect the code base, was it written to be easily testable? Could you easily mock dependencies?
- 34. Untestable Code Not all code is testable If you can’t easily unit test the code base, consider alternatives Functional testing and Acceptance testing are valid options
- 35. Acceptance Testing NOT a replacement for Unit Testing Test large parts of your application at a time Can be harder to pinpoint error location Gives large code coverage in short amount of time
- 36. Digging into the Code Code Consolidation
- 37. Digging into the Code Code Consolidation Replace globals with DI
- 38. Digging into the Code Code Consolidation Replace globals with Dependency Injection Write tests
- 39. Digging into the Code Code Consolidation Replace globals with Dependency Injection Write tests Extract SQL (to ORM or other)
- 40. Digging into the Code Code Consolidation Replace globals with Dependency Injection Write tests Extract SQL (to ORM or other) Extract Business Logic (To domain logic)
- 41. Digging into the Code Code Consolidation Replace globals with Dependency Injection Write tests Extract SQL (to ORM or other) Extract Business Logic (To domain logic) Extract Presentation Logic to Views (Twig, Blade, etc)
- 42. Digging into the Code Code Consolidation Replace globals with Dependency Injection Write tests Extract SQL (to ORM or other) Extract Business Logic (To domain logic) Extract Presentation Logic to Views (Twig, Blade, etc) Extract Action Logic (To Controllers)
- 43. Digging into the Code Code Consolidation Replace globals with Dependency Injection Write tests Extract SQL (to ORM or other) Extract Business Logic (To domain logic) Extract Presentation Logic to Views (Twig, Blade, etc) Extract Action Logic (To Controllers) Write (more) tests
- 46. Where does Laravel fit in?
- 47. You can easily** use Laravel components in your Legacy App ** Relatively speaking, and not all components
- 48. Laravel Component Goals Implement Configuration Implement Logging Implement Routing Implement Database Implement Container
- 54. What about secrets? composer require vlucas/phpdotenv
- 56. Access Config the same way
- 57. Now our config is outside VCS
- 58. Do NOT version control your .env file!
- 61. Logging
- 62. Logging
- 63. You’ll likely want to configure your logger into a base class that is extended
- 68. Routing
- 69. Routing
- 80. Containers are very powerful. Make sure you’re not adding spaghetti code just to shoehorn into your App
- 81. Recap Follow a refactoring process Leverage Laravel components as you refactor Make sure you write tests along the way!
- 82. Joe Ferguson Twitter: @JoePFerguson Email: joe@joeferguson.me Freenode: joepferguson Contact Info: https://joind.in/talk/d306e Feedback: