A couple of days ago, I had the privilege of giving a talk with my colleague Dan at the Symfony UK meetup in London.
Having been a consultant for seven years at eZSystems (the company behind the eZPublish CMS), I felt that one thing that I could share back with the community are the insights I gained while working with a big (at least by php standards), enterprisey, long lived, open source product
The talk, titled “Symfony2 for legacy app rejuvenation: the eZPublish case study” is broadly divided in two parts:
- the first part deals with all the non technical aspects that a huge refactoring project such as this one entails: from having to manage 2 versions of the application for a long period, the possibility of a hostile community fork, to having to pick as foundation a framework with a lively community, which will still be around in 10 years and a rock-stable API guarantee
- the second part is a more detailed explanation of the many things which had to be changed to make the existing CMS codebase integrate with and gradually morph into a pure Symfony full-stack application, from controllers, to database access layers, caching, rest apis, etc…
The target audience is developers mostly, but I strongly believe that being open-minded and removing the barriers which divide the different roles in IT is the way forward to the future – Agile development and DevOps being prime examples of this line of thinking.
I hope you find the talk interesting – the slides have been designed with a lot text compared to the average conference set, specifically to be of value to internet users, not just the attendees.
And don’t worry if you do not get all of the jokes in it, my sense of humour might be slightly more warped than I though. During the whole meetup, no-one laughed!
[Slides] Symfony2 for legacy app rejuvenation: the eZ Publish case study: :