Symfony Day 2009 - Symfony vs Integrating products
β’
1 likeβ’1,428 views
This document provides an overview of when to use a framework versus integrating existing products. It discusses the developer's choice between frameworks and integrated products. Frameworks like Symfony are designed as development platforms and provide more flexibility, while integrated products aim to be usable out of the box but have less flexibility. The document also provides examples of how to integrate Symfony within other products, such as by including Symfony routing rules that direct to an integrated product. It describes how a basic content management system could be developed within Symfony in just one day.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (7)
Similar to Symfony Day 2009 - Symfony vs Integrating products
Similar to Symfony Day 2009 - Symfony vs Integrating products (20)
Recently uploaded
Recently uploaded (20)
Symfony Day 2009 - Symfony vs Integrating products
- 1. Symfony vs. Integrating products when to use a framework Xavier Lacot β Clever Age Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot
- 2. Who I am ξ Symfony developer since end 2005 ξ Several contributions (plugins, docs, patches, etc.) ξ Manager of the PHP Business Unit of Clever Age ξ Clever Age - http://clever-age.com/ ξ Based in Paris, Bordeaux and Lyon, ~70 people ξ Technical architecture expertise ξ Development, ξ Consulting / training / etc. Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 2
- 3. Contents ξ A (web) developer's life ? ξ The choice of a technical architecture ξ A practical sight on CMS and framework's code ξ Howto... ξ Integrate Symfony within other products ξ A CMS with Symfony in less than one day ξ Publication time : cleverMediaLibrary Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 3
- 4. A (web) developer's life Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot http://www.flickr.com/photos/nathonline/918128338 4
- 5. A developer's life ξ Web projects cover a large panel ξ Content management ξ Social networks ξ Customer Relation Management ξ Communication ξ Collaborative ξ File sharing ξ Specific applications ξ In almost every web project, a developer will loose some hair Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 5
- 6. A developer's life ξ Wide range of difficulty ξ 5 days of html integration for a small Β« webpage Β» ξ β¦ 1000+ development days using a framework for a social/2.0 platform ξ Often, the right solution does not exist ! Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 6
- 7. A developer's life ξ The developer has the choice between a lot of tools ξ Frameworks ξ Integrated (open source) products ξ The bad : Integrated (closed-source) products ξ The worse : closed-source frameworks Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 7
- 8. A practical sight on products and framework's code ξ What do I mean with « productsΒ Β» ? ξ CMS, forums, CRM tools, blogs, photo gallery, etc. ξ Not designed as development platforms, but as usable tools ξ Usually only available as packages archives (zip, tar.gz) ξ Not based on a framework Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 8
- 9. A practical sight on products and framework's code ξ ...and with « frameworksΒ Β» ? ξ Not Β« functionalities-oriented Β» ξ Created as a development platform ξ DIY β do it yourself Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 9
- 10. β¦ for instance, Symfony Symfony, a « full optionsΒ Β» framework cli mvc ajax crud cache events routing +600 plugins performance documentation admin generator internationalization unit and functional tests ORMs (Propel or Doctrine) Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 10
- 11. The choice of a technical architecture Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 11
- 12. The choice of a technical architecture Several considerations ξ Complexity of the project (workload, features, scalability) ξ Development methodology ξ Is there a lot of personnalisation ? ξ Adding functions ξ Removing functions ξ Do plugins/extensions exist, that cover the requirements ? Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 12
- 13. Integrating products ξ Integrating products is a good idea ξ It may save time, money, and pressure ξ It may help building a better application ξ At least the client will get the product's feature set ξ Don't always re-invent the wheel ! ξ Perfect solutions for common needs β¦ the hell is that client rarely have common needs ! Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 13
- 14. Integrating products Possible options : ξ Change some code : ξ issues with future upgrades ξ Change code + submit ticket : ξ lot more work (contributions needs to be clean) ξ Not sure it is accepted ξ Create extensions when possible ξ These products are not designed for developing ! ξ Drop the product and code yourself ξ Clearly define the project Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 14
- 15. Β«CMS are good to make simple websites that are mainly meant to be looked at, while frameworks are good to make complex websites that are meant to be interacted withΒ Β» Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 15
- 16. The choice of a technical architecture Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 16
- 17. The choice of a technical architecture ξ Magento Commerce is a sort of success story ξ Based on Zend Framework ξ Overhealmed OS Commerce in 2 years Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 17
- 18. The choice of a technical architecture ξ Gold rules ξ Think simple β not a overload of useless functions ξ Backend must be easy to use ξ WYSIWYG editor ξ Adapted widgets ξ Follow standards β never hack up ξ Documentation ! ξ Open the development : search contributors ξ Release often Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 18
- 19. The choice of a technical architecture ξ The equation is simple : Time to hack vs. Time to build ξ What do you prefer in your life ? Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 19
- 20. A practical sight on products and framework's code Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 20
- 21. A practical sight on products and framework's code ξ The quality largely varies ξ Security ξ A common design pattern (MVC ?) ξ Portability (database, etc.) ξ ORM ξ Developer tools / Technical documentation ξ Performance ξ API ξ Object-oriented ξ Standards compliance Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 21
- 22. For instance : Drupal architecture request Drupal core Modules hooks hook() Theme engine Theme engine (*.tpl.php) Symfony Day β 4. Juni 2009 response Clever Age | Xavier Lacot 22
- 23. For instance : some Drupal facts ξ Forms validation β¦ w00t if (!empty($form_values['departing']) && ( $departing < $date )) { form_set_error('departing', t('The departing date isn't valid.')); } ξ We love documentation... function node_form_submit($form_id, $form_values) { global $user; ... ξ β¦ and also SQL queries ! db_query('DELETE FROM {node} WHERE nid = %d', $node->nid); db_query('DELETE FROM {node_revisions} WHERE nid = %d', $node->nid); ξ ~70 000 lines of PHP code, ~75 files only... Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 23
- 24. A practical sight on products and framework's code ξ Overall criticism : ξ Poorly (well, not) OO ξ No MVC, Modules are a mess ξ No native developer tool, core code is not commented ξ No ORM. The Β« database layer Β» main usage is to map Β« drupal_query() Β» to db specific functions ξ Forms management is archaiq ξ Writing modules might turn into a nightmare β 5000 lines+ of code in a single file, etc. ξ From a purely technical point of view : #FAIL Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 24
- 25. A practical sight on products and framework's code ξ Positive points: ξ It works out of the box ξ If there are very few customizations to do, then it is the prfect solution (no development at all) ξ There is a huge community ξ Lots of contributions ξ /! mot of them are unusable !!! ξ The Β« client effect Β» always works Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 25
- 26. So how to take profit out of both ? Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 26
- 27. How to integrate Symfony with other products ξ Consider the following context ξ Very large company ξ Non-technical people ξ High content management requirements ξ A big part of the site is a custom development ξ We do not have a lot of days ...a common situation Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 27
- 28. How to integrate Symfony with other products ξ Facts: ξ Not possible to develop everything ξ Using the CMS as the development tool won't help ξ => let's integrate Symfony ! Several ways: ξ Include-based integration ξ Several Apache mountpoints ξ XMPP-based communication Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 28
- 29. How to integrate Symfony with other products Module A Module B Symfony ... βcmsβ module databases Drupal install Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 29
- 30. How to integrate Symfony with other products ξ routing.yml, last rule : drupal: url: /:uri param: { module: cms, action: drupal } requirements: { uri: ^(.)*$ } ξ Cms module / executeDrupal() : public function executeDrupal(sfWebRequest $request) { ob_start('drupal'); include(sfConfig::get('sf_root_dir').'/lib/drupal/index.php'); $this->return = ob_get_flush(); } Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 30
- 31. How to integrate Symfony with other products ξ Second solution, XMPP calls for db synchronisation (huge work, but w00t): XMPP server Drupal install Symfony (Openfire) Uses pubSub as data format Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 31
- 32. The one-development-day Symfony CMS Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 32
- 33. A minimal CMS ξ What is a minimal CMS ? ξ Backend ξ Users management, ξ Possibility to create pages at certain urls ξ Posibiliy to put content in these pages ξ Media management ξ Frontend ξ Ability to display informations Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 33
- 34. A minimal CMS ξ Backend components ξ sfDoctrineGuardPlugin ξ cleverMediaLibraryPlugin ξ some tables for the model: content: id: displayed_author: varchar(150) title: varchar(255) body: longvarchar created_at: timestamp created_by: { type: integer, foreignTable: sf_guard_user, foreignReference: id } publication_status: varchar(20) published_at: timestamp published_by: { type: integer, foreignTable: sf_guard_user, foreignReference: id } updated_at: timestamp updated_by: { type: integer, foreignTable: sf_guard_user, foreignReference: id } meta_description: longvarchar meta_keywords: longvarchar Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 34
- 35. A minimal CMS : frontend highlights ξ « catch-allΒ Β» routing rule in routing.yml # for html pages cms: url: /:uri.html param: { module: cms, action: view } requirements: { uri: ^(.)*$ } # for all other defined url cms_garbage: url: /:uri param: { module: cms, action: view } requirements: { uri: ^(.)*$ } Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 35
- 36. Publication time : cleverMediaLibraryPlugin Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 36
- 37. Objectifs ξ An enterprise solution for managing media ξ Supports a large number of file formats ξ Images, videos ξ Documents ξ etc. ξ Storage abstraction ξ Media management API ξ Metadata support ξ Search (tags + index), credentials ξ Performance Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 37
- 38. Formats de fichiers supportΓ©s ξ Images, whatever the type (jpg, gif, png, etc.) ξ Several adapters are available: ξ Imagemagick tools ξ GD ξ PDF documents ξ Office documents ξ OpenOffice ξ MS Office ξ Uses PUNO (PHP β OpenOffice UNO bridge) β not stable ξ Videos ξ Ffmpeg / imagemagick Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 38
- 39. Schema GD ImageMagick PUNO ... adapters handler Adapter Adapter Image PDF Office ... handlers handler handler handler Model classes cleverMedia File storage abstraction - cleverFilesystemPlugin Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 39
- 40. File storage abstraction cleverFileSystemPlugin (1/3) ξ Adapters set ξ Disk ξ FTP ξ S3 ξ β¦ contributions are welcome ! ξ The API is classical ξ Statistics: exists / getSize / isDir / isFile ξ Directories operations: mkDir / listDir / ξ File operations: write / unlink / rename / read / copy Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 40
- 41. File storage abstraction cleverFileSystemPlugin (2/3) ξ File system creation $fs = cleverFilesystem::getInstance(array( 'type' => 'disk', 'root' => '/path/to/root', 'cache_dir' => '/tmp' )); // filesystem operations $content = $fs->listDir(''); $content = $fs->listDir('path/to/directory'); Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 41
- 42. File storage abstraction cleverFileSystemPlugin (3/3) $fs = cleverFilesystem::getInstance('ftp_michel'); app: cleverFilesystemPlugin: filesystems: ftp_michel: cache_dir: /tmp type: ftp host: localhost username: michel password: p4ssw0rd Port: 21 root: ftpserv ftp://michel:p4ssw0rd@localhost:21/ftpserv/ Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 42
- 43. API usage // retrieve a folder $parent = ccMediaFolderPeer::retrieveByPath('meetings/cologne'); // Create a folder $folder = new ccMediaFolder(); $fields = array( 'name' => 'Symfony Day Cologne', 'created_by' => $this->getUser()->getUserId(), 'updated_by' => $this->getUser()->getUserId() 'parent' => $parent ); $folder->update($fields); $folder->save(); Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 43
- 44. API usage // retrieve a folder $parent = ccMediaFolderPeer::retrieveByPath('meetings/cologne'); // Create a file $image = new ccMedia(); $fields = array( 'cc_media_folder' => $folder, 'source' => 'http://lacot.org/image.png', 'filename' => 'new_filename.png', 'updated_by' => $this->getUser()->getUserId(), 'created_by' => $this->getUser()->getUserId() ); $image->update($fields); $image->save(); Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 44
- 45. tasks Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 45
- 46. Questions Xavier Lacot <xavier@lacot.org> http://lacot.org/ Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 46
- 47. Contact us Clever Age : 37, boulevard des Capucines 75002 Paris, France Agencies : Lyon, Bordeaux Phone : +33 1 53 34 66 10 Web : http://www.clever-age.com/ Commercial contact : commercial@clever-age.com Technical contact : technique@clever-age.com Symfony Day β 4. Juni 2009 Clever Age | Xavier Lacot 47