Migration of a legacy project to Symfony
0 likes323 views
This document discusses migrating a legacy project to the Symfony framework. It begins by explaining why a dual side-by-side migration is preferable to a complete rewrite. It then provides details on how to get started, such as bootstrapping the legacy application and creating a dynamic router. It also covers migrating HTML/assets, accessing legacy services, and taking an iterative approach by refactoring parts of the codebase at a time. Overall, the key benefits highlighted are lower risk, continuous development, and easier adoption of best practices compared to a full rewrite.
![www.pixelfederation.com
Migration of a legacy projectto Symfony
How did we start?
Create your router - using Dynamic Router
DynamicRouter - http://symfony.com/doc/current/cmf/bundles/routing/dynamic.html
• This router implementation is configured to load routes from a RouteProviderInterface.
• You will have ChainRouter instead of Router in @router service
• ChainRouter has configuration of routers by ID
• router.default (origin router) [with top of priority]
• cmf_routing.dynamic_router
• Dynamic router has dependency on RouteProviderInterface
• Create own class implementing the RouteProviderInterface
• You need to create FinalMatcher, because all requests try to match by path info](https://image.slidesharecdn.com/migrationofalegacyprojecttosymfony-190306075440/85/Migration-of-a-legacy-project-to-Symfony-9-320.jpg)
![www.pixelfederation.com
Migration of alegacy projectto Symfony
How did we start?
Aliases of old routes to a new ones
Example of route:
Our legacy “FW” uses the “a” param from GET/POST this way: “?a=api-filelist/init”
1.Created an instance of the original ApiFileList controller in the boot() method [previous slide]
2.The controller was injected into the Symfony container
3.This request created an instance of the old ApiFilelistController
4.Created ApiFilelistController in Symfony as well - naming conventions don't matter
5.Implemented an action e.g. initAction
?a=api-filelist/init === ApiFilelist_init
The following annotation should be used on this method:
@RestPost("/device/api-filelist/init", name=“ApiFilelist_init”)
Now your controllers in Symfony listen to legacy request.
Second option:
1.create only a proxy to the old server
2.get instance of a legacy controller from the container
3.call the controller action](https://image.slidesharecdn.com/migrationofalegacyprojecttosymfony-190306075440/85/Migration-of-a-legacy-project-to-Symfony-10-320.jpg)
![www.pixelfederation.com
Migration of legacy projectto Symfony
What else?
HTML Front - End
Migrate all HTML outputs and assets to Symfony - I recommend it.
Access from Symfony to legacy services?
Old services are registered in “dic” (Pimple)
Usage in the old server code: $dic[AppServiceLocalizations::class];
Usage in Symfony services.yml: ‘@=service("dic").offsetGet("AppServiceLocalizations")'
Autowire old services to new Symfony services
service.yaml
AppServiceLocalizations:
factory: 'PixelFederationBundleServerMigrationBundleServiceDicFactoryProxy:factoryService'
arguments: ['AppServiceLocalizations']](https://image.slidesharecdn.com/migrationofalegacyprojecttosymfony-190306075440/85/Migration-of-a-legacy-project-to-Symfony-11-320.jpg)
![[2019] 퍼즐 게임 난이도 예측은 닥터 P에게](https://cdn.slidesharecdn.com/ss_thumbnails/nhnforward20194-200121085244-thumbnail.jpg?width=560&fit=bounds)
Ad
More Related Content
What's hot (20)
Similar to Migration of a legacy project to Symfony (20)
Ad
More from Pixel Federation (6)
Ad
Recently uploaded (20)
![Download Wondershare Filmora Crack [2025] With Latest](https://cdn.slidesharecdn.com/ss_thumbnails/neo4j-howkgsareshapingthefutureofgenerativeaiatawssummitlondonapril2024-240426125209-2d9db05d-250419-250428115407-a04afffa-thumbnail.jpg?width=560&fit=bounds)
![Get & Download Wondershare Filmora Crack Latest [2025]](https://cdn.slidesharecdn.com/ss_thumbnails/revolutionizingresidentialwi-fi-250422112639-60fb726f-250429170801-59e1b240-thumbnail.jpg?width=560&fit=bounds)
Migration of a legacy project to Symfony
- 1. Migration of a legacy project to Symfony Juraj Šurman <[email protected]> 21.02.2019
- 2. www.pixelfederation.com Migration of a legacy projectto Symfony What does "Spaghetti code" mean? Opposite of SOLID => STUPID • Singleton • Tight Coupling • Untestability • Premature Optimization • Indescriptive Naming • Duplication
- 3. www.pixelfederation.com Migration of a legacy projectto Symfony What "Spaghetti code" means?
- 4. www.pixelfederation.com Migration of a legacy projectto Symfony REFACTORING !!! ???
- 5. www.pixelfederation.com Migration of a legacy projectto Symfony Why dual side by side migration of the project? Why not rewritting everything from scratch? A valid question, but: •no time (or too little) for complete rewrite in production •business value is questionable for the business owner/producer •risk of introducing new errors into production •complex framework hacking to glue both systems together What are the pros actually? •Continuous transition + Continuous development on existing code •Lower risk of introducing global errors, smaller errors with smaller impact still possible •Faster and easier deployment into production •It is easier to rewrite it part by part - in small chunks •=== You will have a less nervous producer = almost happy :) ===
- 6. www.pixelfederation.com Migration of a legacy projectto Symfony Why Symfony? There are so many Frameworks … why Symfony? • one of the best PHP Frameworks • developers more skilled than us design and maintain the framework • ongoing development with guaranteed backwards compatibility • we use it on new internal projects • supported by SensioLabs • highest quality code base in open source PHP world • creates best practices • integration of many libraries through bundles out of the box
- 7. www.pixelfederation.com Migration of a legacy projectto Symfony How did we start? Boot legacy app The main idea is to have one bundle where you implement boot() where you boot the legacy app. Or when you are using symfony 4 override boot() in your AppKernel.php
- 8. www.pixelfederation.com Migration of a legacy projectto Symfony
- 9. www.pixelfederation.com Migration of a legacy projectto Symfony How did we start? Create your router - using Dynamic Router DynamicRouter - http://symfony.com/doc/current/cmf/bundles/routing/dynamic.html • This router implementation is configured to load routes from a RouteProviderInterface. • You will have ChainRouter instead of Router in @router service • ChainRouter has configuration of routers by ID • router.default (origin router) [with top of priority] • cmf_routing.dynamic_router • Dynamic router has dependency on RouteProviderInterface • Create own class implementing the RouteProviderInterface • You need to create FinalMatcher, because all requests try to match by path info
- 10. www.pixelfederation.com Migration of alegacy projectto Symfony How did we start? Aliases of old routes to a new ones Example of route: Our legacy “FW” uses the “a” param from GET/POST this way: “?a=api-filelist/init” 1.Created an instance of the original ApiFileList controller in the boot() method [previous slide] 2.The controller was injected into the Symfony container 3.This request created an instance of the old ApiFilelistController 4.Created ApiFilelistController in Symfony as well - naming conventions don't matter 5.Implemented an action e.g. initAction ?a=api-filelist/init === ApiFilelist_init The following annotation should be used on this method: @RestPost("/device/api-filelist/init", name=“ApiFilelist_init”) Now your controllers in Symfony listen to legacy request. Second option: 1.create only a proxy to the old server 2.get instance of a legacy controller from the container 3.call the controller action
- 11. www.pixelfederation.com Migration of legacy projectto Symfony What else? HTML Front - End Migrate all HTML outputs and assets to Symfony - I recommend it. Access from Symfony to legacy services? Old services are registered in “dic” (Pimple) Usage in the old server code: $dic[AppServiceLocalizations::class]; Usage in Symfony services.yml: ‘@=service("dic").offsetGet("AppServiceLocalizations")' Autowire old services to new Symfony services service.yaml AppServiceLocalizations: factory: 'PixelFederationBundleServerMigrationBundleServiceDicFactoryProxy:factoryService' arguments: ['AppServiceLocalizations']
- 12. www.pixelfederation.com Migration of legacy projectto Symfony Next steps? Rewrite, test, production, rewrite, test, production, rewrite… • Start refactoring with services which are needed to be changed, because of a new feature or some optimisation -> move refactored services from legacy namespace to the “correct/clear” place for better distinguishing
- 13. www.pixelfederation.com Migration of legacy projectto Symfony What have we learned? It’s easy (now) - you can start right now :) • just don't be afraid to do it (of course, your boss must know about it and agree with it) • If we use Symfony in our projects, we will able to use compatible packages developed by us and by the world community • Better programmer recycling (moving between projects) • We will not have a rigid framework - The world community is developing it • Easier to use current best practices - we do not need to develop them on our own • New programmers are introduced into the developing process more easily (they already know the technologies) • Programmer has maximum time on project (creative part of work) instead of reading of tons and tons of spaghetti code • Framework Documentation + stack overflow • Tons of bundles/plugins/modules
- 14. www.pixelfederation.com Migration of a legacy projectto Symfony Thank you.