SymfonyCon Cluj 2017 - Symfony at OpenSky
•
0 likes•634 views
- OpenSky is a digital agency that uses Symfony to power multiple e-commerce businesses, with over 100 employees in offices around the world. - They have been using Symfony since 2010, initially migrating from Magento to Symfony 1 and then Symfony 2. - Their current stack includes Symfony 2.8, PHP 7.1, MySQL, MongoDB, Redis, and over 10,000 unit tests.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to SymfonyCon Cluj 2017 - Symfony at OpenSky
Similar to SymfonyCon Cluj 2017 - Symfony at OpenSky (20)
More from Pablo Godel
More from Pablo Godel (20)
Recently uploaded
Recently uploaded (20)
SymfonyCon Cluj 2017 - Symfony at OpenSky
- 1. Symfony @ OpenSky Pablo Godel
- 2. Symfony @ OpenSky What is OpenSky?
- 3. Symfony @ OpenSky What is OpenSky? • Multiple businesses powered by Symfony: 1. opensky.com 2. dotandbo.com 3. 55mulberry.com
- 4. Symfony @ OpenSky What is OpenSky? • Multiple businesses powered by Symfony: 1. opensky.com 2. dotandbo.com 3. 55mulberry.com • +100 employees
- 5. Symfony @ OpenSky What is OpenSky? • Multiple businesses powered by Symfony: 1. opensky.com 2. dotandbo.com 3. 55mulberry.com • +100 employees • Offices all around the world in New York, Portland, Nashville, Miami, Chico, Bucharest and Los Angeles
- 8. Symfony @ OpenSky • Early adopter of Symfony2 in 2010 before 2.0 stable was released History
- 9. Symfony @ OpenSky • Early adopter of Symfony2 in 2010 before 2.0 stable was released • Migrated from Magento -> symfony1 -> Symfony2 History
- 10. Symfony @ OpenSky • Early adopter of Symfony2 in 2010 before 2.0 stable was released • Migrated from Magento -> symfony1 -> Symfony2 • Aspects of Magento cart utilized throughout migration process until completely phased out with proprietary cart/checkout technology History
- 11. Symfony @ OpenSky THE CURRENT STACK
- 12. Symfony @ OpenSky • Symfony 2.8 • RequireJS + Backbone • PHP 7.1.10 • MySQL 5.6 + MongoDB 3.2 • Redis • Varnish + Nginx • VMWare • Vagrant + VirtualBox for Dev VMs The Current Stack
- 13. Symfony @ OpenSky • ~400 Controllers • +800 Routes • ~1,900 Services • 285 Commands • 374 Entities • 467 Documents • 808,532 LoC • 3,738 Classes • 156 Interfaces • 46 Traits • +10,000 Unit Tests The Current Stack
- 14. Symfony @ OpenSky The Current Stack
- 15. Symfony @ OpenSky The Current Stack
- 16. Symfony @ OpenSky CODING WORKFLOW
- 17. Symfony @ OpenSky Symfony at OpenSky GitHub Enterprise GitHub Enterprise Coding workflow
- 18. Symfony @ OpenSky • production branch (master) Coding workflow
- 19. Symfony @ OpenSky • production branch (master) • feature / fix branches Coding workflow
- 20. Symfony @ OpenSky • production branch (master) • feature / fix branches • Pull Requests linked to JIRA Coding workflow
- 21. Symfony @ OpenSky • production branch (master) • feature / fix branches • Pull Requests linked to JIRA • Integration with Jenkins for Unit/ Functional Tests Coding workflow
- 22. Symfony @ OpenSky • production branch (master) • feature / fix branches • Pull Requests linked to JIRA • Integration with Jenkins for Unit/ Functional Tests • Pre-commit Hooks for php-cs-fixer, gulp-jshint, gulp-sass-lint Coding workflow
- 23. Symfony @ OpenSky • Symfony Coding Standards Coding workflow
- 24. Symfony @ OpenSky • Symfony Coding Standards • Short Array Syntax Coding workflow
- 25. Symfony @ OpenSky • Symfony Coding Standards • Short Array Syntax • Ordered Use Statements Coding workflow
- 26. Symfony @ OpenSky • Symfony Coding Standards • Short Array Syntax • Ordered Use Statements • Ensuring an EOL at end of file Coding workflow
- 27. Symfony @ OpenSky • Symfony Coding Standards • Short Array Syntax • Ordered Use Statements • Ensuring an EOL at end of file • SQL Style Guide - http://www.sqlstyle.guide/ Coding workflow
- 28. Symfony @ OpenSky • PHP7 Type-Hints when possible Coding workflow
- 29. Symfony @ OpenSky • PHP7 Type-Hints when possible • DocBlocks only when adds clarity Coding workflow
- 30. Symfony @ OpenSky • PHP7 Type-Hints when possible • DocBlocks only when adds clarity • ClassName::class Coding workflow
- 31. Symfony @ OpenSky • PHP7 Type-Hints when possible • DocBlocks only when adds clarity • ClassName::class • ‘NamespaceClassName’ Coding workflow
- 32. Symfony @ OpenSky • PHP7 Type-Hints when possible • DocBlocks only when adds clarity • ClassName::class • ‘NamespaceClassName’ • In forms use class constant Coding workflow
- 33. Symfony @ OpenSky • PHP7 Type-Hints when possible • DocBlocks only when adds clarity • ClassName::class • ‘NamespaceClassName’ • In forms use class constant • $builder->add('name', TextType::class); Coding workflow
- 34. Symfony @ OpenSky • PHP7 Type-Hints when possible • DocBlocks only when adds clarity • ClassName::class • ‘NamespaceClassName’ • In forms use class constant • $builder->add('name', TextType::class); • Always use ‘use’ statement • $time = new DateTime() Coding workflow
- 35. Symfony @ OpenSky Before production deployment: Coding workflow
- 36. Symfony @ OpenSky Before production deployment: • Peer Reviews using GitHub PRs Coding workflow
- 37. Symfony @ OpenSky Before production deployment: • Peer Reviews using GitHub PRs • 100% test pass (unit & functional) Coding workflow
- 38. Symfony @ OpenSky Before production deployment: • Peer Reviews using GitHub PRs • 100% test pass (unit & functional) • Integration deploy/testing Coding workflow
- 39. Symfony @ OpenSky Before production deployment: • Peer Reviews using GitHub PRs • 100% test pass (unit & functional) • Integration deploy/testing • UA / QA pass (tracked in JIRA) Coding workflow
- 40. Symfony @ OpenSky SYMFONY BUNDLES
- 41. Symfony @ OpenSky • Split things into broad bundles. Don’t over bundle. Symfony Bundles
- 42. Symfony @ OpenSky • Split things into broad bundles. Don’t over bundle. • MainBundle Symfony Bundles
- 43. Symfony @ OpenSky • Split things into broad bundles. Don’t over bundle. • MainBundle • AdminBundle (500+ routes, 300 extra services in the container) Symfony Bundles
- 44. Symfony @ OpenSky • Split things into broad bundles. Don’t over bundle. • MainBundle • AdminBundle (500+ routes, 300 extra services in the container) • APIBundle Symfony Bundles
- 45. Symfony @ OpenSky • Split things into broad bundles. Don’t over bundle. • MainBundle • AdminBundle (500+ routes, 300 extra services in the container) • APIBundle • 3rd Party Bundles Symfony Bundles
- 46. Symfony @ OpenSky • Split things into broad bundles. Don’t over bundle. • MainBundle • AdminBundle (500+ routes, 300 extra services in the container) • APIBundle • 3rd Party Bundles • AvalancheImagineBundle Symfony Bundles
- 47. Symfony @ OpenSky • Split things into broad bundles. Don’t over bundle. • MainBundle • AdminBundle (500+ routes, 300 extra services in the container) • APIBundle • 3rd Party Bundles • AvalancheImagineBundle • FOSUserBundle Symfony Bundles
- 48. Symfony @ OpenSky • Split things into broad bundles. Don’t over bundle. • MainBundle • AdminBundle (500+ routes, 300 extra services in the container) • APIBundle • 3rd Party Bundles • AvalancheImagineBundle • FOSUserBundle • Using 3rd party bundles may impact maintainability in the long term Symfony Bundles
- 50. Symfony @ OpenSky • MongoDB and MySQL together Doctrine
- 51. Symfony @ OpenSky • MongoDB and MySQL together • References between MongoDB and MySQL Doctrine
- 52. Symfony @ OpenSky • MongoDB and MySQL together • References between MongoDB and MySQL • Using the Doctrine ORM & MongoDB ODM to make the models for the two databases transparent to the application. Doctrine
- 53. Symfony @ OpenSky • MongoDB and MySQL together • References between MongoDB and MySQL • Using the Doctrine ORM & MongoDB ODM to make the models for the two databases transparent to the application. • Never delete data due to referential integrity problems. Use soft delete (deletedAt) Doctrine
- 54. Symfony @ OpenSky • MongoDB and MySQL together • References between MongoDB and MySQL • Using the Doctrine ORM & MongoDB ODM to make the models for the two databases transparent to the application. • Never delete data due to referential integrity problems. Use soft delete (deletedAt) • Traits for common functionality like createdAt/ updatedAt/deletedAt Doctrine
- 56. Symfony @ OpenSky • How long did it take to run? Doctrine Migrations
- 57. Symfony @ OpenSky • How long did it take to run? • Is it backwards compatible? Doctrine Migrations
- 58. Symfony @ OpenSky • How long did it take to run? • Is it backwards compatible? • Up & Down Doctrine Migrations
- 59. Symfony @ OpenSky • How long did it take to run? • Is it backwards compatible? • Up & Down • schema.sql / data.sql up-to-date Doctrine Migrations
- 60. Symfony @ OpenSky • How long did it take to run? • Is it backwards compatible? • Up & Down • schema.sql / data.sql up-to-date • Add indexes Doctrine Migrations
- 61. Symfony @ OpenSky • How long did it take to run? • Is it backwards compatible? • Up & Down • schema.sql / data.sql up-to-date • Add indexes • Remove data later in separate migration Doctrine Migrations
- 62. Symfony @ OpenSky SYMFONY MISC
- 63. Symfony @ OpenSky • Lean Controllers
- 64. Symfony @ OpenSky • Lean • No Business Logic Controllers
- 65. Symfony @ OpenSky • Lean • No Business Logic • Only Flow control Controllers
- 66. Symfony @ OpenSky • Lean • No Business Logic • Only Flow control • Extend Custom BaseController Controllers
- 67. Symfony @ OpenSky • Two tiers of authentication implemented using role voters. Security
- 68. Symfony @ OpenSky • Two tiers of authentication implemented using role voters. • PartiallyAuthenticatedVoter Security
- 69. Symfony @ OpenSky • Two tiers of authentication implemented using role voters. • PartiallyAuthenticatedVoter • AuthenticatedRecentlyVoter Security
- 70. Symfony @ OpenSky • Two tiers of authentication implemented using role voters. • PartiallyAuthenticatedVoter • AuthenticatedRecentlyVoter • When a user is recently authenticated, they are logged in to 2nd tier of authentication and have access to account, checkout, etc. After 15 minutes of inactivity, user is logged out of 2nd tier. Security
- 71. Symfony @ OpenSky • Two tiers of authentication implemented using role voters. • PartiallyAuthenticatedVoter • AuthenticatedRecentlyVoter • When a user is recently authenticated, they are logged in to 2nd tier of authentication and have access to account, checkout, etc. After 15 minutes of inactivity, user is logged out of 2nd tier. • Admin integrates with LDAP (using zendframework/ zend-ldap) Security
- 72. Symfony @ OpenSky • Two tiers of authentication implemented using role voters. • PartiallyAuthenticatedVoter • AuthenticatedRecentlyVoter • When a user is recently authenticated, they are logged in to 2nd tier of authentication and have access to account, checkout, etc. After 15 minutes of inactivity, user is logged out of 2nd tier. • Admin integrates with LDAP (using zendframework/ zend-ldap) • Multiple firewalls/authentication providers for consumer facing, admin and api. Security
- 73. Symfony @ OpenSky Runtime Settings/Parameters • Parameters defined in config/parameters.yml
- 74. Symfony @ OpenSky • Parameters defined in config/parameters.yml • Override stored in MongoDB Runtime Settings/Parameters
- 75. Symfony @ OpenSky • Parameters defined in config/parameters.yml • Override stored in MongoDB • Parameters can have start & end datetime Runtime Settings/Parameters
- 76. Symfony @ OpenSky • Parameters defined in config/parameters.yml • Override stored in MongoDB • Parameters can have start & end datetime • All parameters stored in cache Runtime Settings/Parameters
- 77. Symfony @ OpenSky • Parameters defined in config/parameters.yml • Override stored in MongoDB • Parameters can have start & end datetime • All parameters stored in cache • When parameter value is changed, cache is updated and queue workers restarted Runtime Settings/Parameters
- 78. Symfony @ OpenSky • Parameters defined in config/parameters.yml • Override stored in MongoDB • Parameters can have start & end datetime • All parameters stored in cache • When parameter value is changed, cache is updated and queue workers restarted • Allows for configuration changes without deployment Runtime Settings/Parameters
- 79. Symfony @ OpenSky • Parameters defined in config/parameters.yml • Override stored in MongoDB • Parameters can have start & end datetime • All parameters stored in cache • When parameter value is changed, cache is updated and queue workers restarted • Allows for configuration changes without deployment • Heavily used for feature flags and enable/ disable of new features Runtime Settings/Parameters
- 80. Symfony @ OpenSky Runtime Settings/Parameters
- 81. Symfony @ OpenSky Runtime Settings/Parameters
- 82. Symfony @ OpenSky Runtime Settings/Parameters
- 84. Symfony @ OpenSky • Perform tasks after the response has been sent to client Event kernel.terminate
- 85. Symfony @ OpenSky • Perform tasks after the response has been sent to client • Store Request Log in MongoDB Collection Event kernel.terminate
- 86. Symfony @ OpenSky • Perform tasks after the response has been sent to client • Store Request Log in MongoDB Collection • Analyze request for further actions Event kernel.terminate
- 87. Symfony @ OpenSky • Perform tasks after the response has been sent to client • Store Request Log in MongoDB Collection • Analyze request for further actions • Only effective with FastCGI Event kernel.terminate
- 88. Symfony @ OpenSky • Queueing events for async functionality Events system
- 89. Symfony @ OpenSky • Queueing events for async functionality • Event serializer/unserializer Events system
- 90. Symfony @ OpenSky • Queueing events for async functionality • Event serializer/unserializer • Scheduling events Events system
- 91. Symfony @ OpenSky • Queueing events for async functionality • Event serializer/unserializer • Scheduling events • Event retries, retry max amount Events system
- 92. Symfony @ OpenSky • Queueing events for async functionality • Event serializer/unserializer • Scheduling events • Event retries, retry max amount • One queue per mongodb collection Events system
- 93. Symfony @ OpenSky • Queueing events for async functionality • Event serializer/unserializer • Scheduling events • Event retries, retry max amount • One queue per mongodb collection • Queue workers managed with Supervisord Events system
- 94. Symfony @ OpenSky Events system
- 95. Symfony @ OpenSky Events system
- 96. Symfony @ OpenSky Events system
- 97. Symfony @ OpenSky Events system
- 98. Symfony @ OpenSky Events system
- 100. Symfony @ OpenSky • php-kip using yabot Slack integration
- 101. Symfony @ OpenSky • php-kip using yabot • Production deploy queue/line Slack integration
- 102. Symfony @ OpenSky • php-kip using yabot • Production deploy queue/line • Dev environment reservations & deploys Slack integration
- 103. Symfony @ OpenSky Symfony at OpenSky Php-kip using yubot - Production deploy queue/line - Dev environment deploys Slack integration
- 104. Symfony @ OpenSky Symfony at OpenSky Php-kip using yubot - Production deploy queue/line - Dev environment deploys Slack integration
- 105. Symfony @ OpenSky Symfony at OpenSky Php-kip using yubot - Production deploy queue/line - Dev environment deploys Slack integration
- 106. Symfony @ OpenSky Slack integration
- 107. Symfony @ OpenSky Slack integration
- 108. Symfony @ OpenSky Slack integration
- 110. Symfony @ OpenSky Search • Integration with Algolia
- 111. Symfony @ OpenSky • Integration with Algolia • algolia/algoliasearch-client-php Search
- 112. Symfony @ OpenSky • Integration with Algolia • algolia/algoliasearch-client-php • Update index through async Event Listeners Search
- 113. Symfony @ OpenSky Payments • Integration with Braintree Payments • braintree/braintree_php
- 114. Symfony @ OpenSky • NPM • jQuery • RequireJS • Backbone • TwigJS • Gulp / Less / Sass The Frontend
- 115. Symfony @ OpenSky • A/B Split Testing using Optimizely for testing UI/UX changes • Send small % of traffic to new features • GoogleAnalytics tracking conversion rate The Frontend
- 117. Symfony @ OpenSky • pr-nightmare Testing
- 118. Symfony @ OpenSky • pr-nightmare • Runs on all commits and pull requests Testing
- 119. Symfony @ OpenSky • pr-nightmare • Runs on all commits and pull requests • Uses PHPChunkit to run 30 minutes of tests in 3 minutes by running groups of tests in parallel across multiple servers. https://github.com/jwage/phpchunkit Testing
- 120. Symfony @ OpenSky • pr-nightmare • Runs on all commits and pull requests • Uses PHPChunkit to run 30 minutes of tests in 3 minutes by running groups of tests in parallel across multiple servers. https://github.com/jwage/phpchunkit • Selenium for browser functional testing Testing
- 122. Symfony @ OpenSky • ‘@app admin’ annotation to indicate web test cases which app/kernel to boot up Testing with PHPUnit
- 123. Symfony @ OpenSky • ‘@app admin’ annotation to indicate web test cases which app/kernel to boot up • AutoDataCleanupListener keeps tracks of what collections and tables were inserted to in a test and cleans up afterwards. This used to be explicitly required by the developer but happens automatically now Testing with PHPUnit
- 124. Symfony @ OpenSky • ‘@app admin’ annotation to indicate web test cases which app/kernel to boot up • AutoDataCleanupListener keeps tracks of what collections and tables were inserted to in a test and cleans up afterwards. This used to be explicitly required by the developer but happens automatically now • AbstractTwigLintTest: Twig linting. Loads up all twig files to make sure there are no parse errors Testing with PHPUnit
- 125. Symfony @ OpenSky • ‘@app admin’ annotation to indicate web test cases which app/kernel to boot up • AutoDataCleanupListener keeps tracks of what collections and tables were inserted to in a test and cleans up afterwards. This used to be explicitly required by the developer but happens automatically now • AbstractTwigLintTest: Twig linting. Loads up all twig files to make sure there are no parse errors • Generating unit tests from class definitions Testing with PHPUnit
- 126. Symfony @ OpenSky • ‘@app admin’ annotation to indicate web test cases which app/kernel to boot up • AutoDataCleanupListener keeps tracks of what collections and tables were inserted to in a test and cleans up afterwards. This used to be explicitly required by the developer but happens automatically now • AbstractTwigLintTest: Twig linting. Loads up all twig files to make sure there are no parse errors • Generating unit tests from class definitions • PHPUnit watch command Testing with PHPUnit
- 127. Symfony @ OpenSky Testing with PHPUnit
- 128. Symfony @ OpenSky Testing with PHPUnit
- 129. Symfony @ OpenSky PHPUnit watch
- 130. Symfony @ OpenSky PHPUnit watch
- 131. Symfony @ OpenSky PHPUnit watch
- 132. Symfony @ OpenSky PHPUnit watch
- 133. Symfony @ OpenSky Twig Lint with PHPUnit
- 134. Symfony @ OpenSky Twig Lint with PHPUnit
- 135. Symfony @ OpenSky Twig Lint with PHPUnit
- 137. Symfony @ OpenSky Deployment • Use Customized Fabric • Manually started from Jenkins • First build task • Merge feature/fix branch into master • Create Tag
- 138. Symfony @ OpenSky • Final build task • git checkout • composer install --no-dev —no-scripts • Build front controller • Run gulp, requires, less, sass • Warmup cache for each app • Assetic dump • Build artifacts file & distribute it to servers • Run MySQL & MongoDB Migrations • Rotate logs • Restart php-fpm • Reload Varnish and nginx • Restart queue workers Deployment • Use Customized Fabric • Manually started from Jenkins • First build task • Merge feature/fix branch into master • Create Tag
- 140. Symfony @ OpenSky Thank you! Pablo Godel @pgodel http://slideshare.net/pgodel https://joind.in/talk/ede0c We are hiring! jobs@opensky.com