Unglue All The Things! Symfony Live! London 2016

Bundles. Packages. Modules. Plugins. So much code is locked up in framework-specific packages. With so may people talking about wanting to write framework agnostic packages, it can be easy to get stuck thinking that this is, and should always be, the end goal. Learn about one developer's experience trying to write truly framework agnostic code. See what worked, what didn't, and walk away having a better idea how you, too, can attempt to unglue all the things!

Transcript

1. Unglue All The Things! Beau Simensen • beau.io • @beausimensen
2. Framework Agnostic PHP Packages
4. Models
6. Reality
7. Active Record is the worst
8. Doctrine is just as bad
9. Event Sourcing
10. Roll Your Own
11. Don't kid yourself.
12. Lessons Learned ORM framework agnostic models are hard to get right in the real world
13. Lessons Learned ORM framework agnostic models will most likely require compromises
14. Lessons Learned Rolling your own ORM framework does not make your model framework agnostic
16. Symfony 2
17. Bundles.
18. "Modern PHP Packages"
19. Yuck.
20. Too many conventions
21. Too complicated
22. Too much "Symfony" noise around my Business Logic
23. Silex
24. Silex Service Providers Fancy classes that wire up Pimple
27. { "require": { "symfony/framework-bundle" : "~3.0|~2.0" } }
28. { "require": { "symfony/asset": "~2.8|~3.0", "symfony/cache": "~3.2", "symfony/class-loader": "~3.2", "symfony/dependency-injection": "~3.2", "symfony/config": "~2.8|~3.0", "symfony/event-dispatcher": "~2.8|~3.0", "symfony/http-foundation": "~3.1", "symfony/http-kernel": "~3.2", "symfony/polyfill-mbstring": "~1.0", "symfony/filesystem": "~2.8|~3.0", "symfony/finder": "~2.8|~3.0", "symfony/routing": "~3.0", "symfony/security-core": "~3.2", "symfony/security-csrf": "~2.8|~3.0", "symfony/stopwatch": "~2.8|~3.0", "symfony/templating": "~2.8|~3.0", "symfony/translation": "~2.8|~3.0", "doctrine/cache": "~1.0", "doctrine/annotations": "~1.0" } }
29. acme/gravatar-provider Yay!
30. { "require": { "ornicar/gravatar-bundle" : "^1.0" } }
31. Nope.
32. Premature Optimisation
33. Does the code I'm writing have any value on its own?
34. Am I splitting my packages too far?
35. npm install left-pad
36. Is copying and pasting code going to be the lesser of two evils?
38. Silex + Doctrine
39. dflydev/doctrine-orm-service-provider
40. My Goal: Ship mappings that required no configuration changes
41. # app/config/config.yml doctrine: orm: entity_managers: default: mappings: acme: type: annotation prefix: Acme\Entity dir: "%kernel.root_dir%/../vendor/acme/entity/src/Entity" is_bundle: false
42. Problem.
43. Do we already have the tools to solve this problem?
44. PSR-0 (with a little help from Composer)
45. "autoload": { "psr-0": { "Monii\\Deal\\": "src" } }
46. "autoload": { "psr-0": { "Monii\\Deal\\": "src" } } Monii\Deal\DealRepository => src/Monii/Deal/DealRepository.php
47. "autoload": { "psr-0": { "Monii\\Deal\\": "src" } } Monii\Deal\DealRepository => src/Monii/Deal/DealRepository.php Monii\Deal\DealRepository => vendor/monii/deal/src/Monii/Deal/DealRepository.php
48. What if we used PSR-0 mappings and rules to locate other types of files than just classes?
49. "autoload": { "psr-0": { "Monii\\Deal\\": "src" } } Monii\Deal\DealRepository => src/Monii/Deal/DealRepository.php
50. "autoload": { "psr-0": { "Monii\\Deal\\": "src" } } Monii\Deal\DealRepository => src/Monii/Deal/DealRepository.php classpath:Monii/Deal/resources/mapping.yml => src/Monii/Deal/resources/mapping.yml
51. "autoload": { "psr-0": { "Monii\\Deal\\": "src" } } Monii\Deal\DealRepository => src/Monii/Deal/DealRepository.php classpath:Monii/Deal/resources/mapping.yml => src/Monii/Deal/resources/mapping.yml classpath:Monii/Deal/resources/mapping.yml => vendor/monii/deal/src/Monii/Deal/resources/mapping.yml
52. dflydev/psr0-resource-locator
53. $container["orm.em.options"] = [ "mappings" => [ [ "type" => "xml", "namespace" => "Monii\Deal", "resources_namespace" => "Monii\Deal\mappings", ], ], ];
54. $container["orm.em.options"] = [ "mappings" => [ [ "type" => "xml", "namespace" => "Monii\Deal", "resources_namespace" => "Monii\Deal\mappings", ], ], ]; Monii\Deal\Deal
55. $container["orm.em.options"] = [ "mappings" => [ [ "type" => "xml", "namespace" => "Monii\Deal", "resources_namespace" => "Monii\Deal\mappings", ], ], ]; Monii\Deal\Deal => classpath:Monii/Deal/mappings/Deal.xml
56. $container["orm.em.options"] = [ "mappings" => [ [ "type" => "xml", "namespace" => "Monii\Deal", "resources_namespace" => "Monii\Deal\mappings", ], ], ]; Monii\Deal\Deal => classpath:Monii/Deal/mappings/Deal.xml => vendor/monii/deal/src/Monii/Deal/mappings/Deal.xml
57. PSR-4
58. Shorter paths please! — Everyone, apparently
59. "autoload": { "psr-0": { "Monii\\Deal\\": "src" } }
60. "autoload": { "psr-4": { "Monii\\Deal\\": "src" } }
61. "autoload": { "psr-4": { "Monii\\Deal\\": "src" } } Monii\Deal\DealRepository => src/DealRepository.php Monii\Deal\DealRepository => vendor/monii/deal/src/DealRepository.php
62. "autoload": { "psr-4": { "Monii\\Deal\\": "src" } }
63. "autoload": { "psr-4": { "Monii\\Deal\\": "src", "Monii\\Deal\\resources": "resources" } }
64. "autoload": { "psr-4": { "Monii\\Deal\\": "src", "Monii\\Deal\\resources": "resources" } } classpath:Monii/Deal/resources/mapping.yml => resources/mapping.yml
65. "autoload": { "psr-4": { "Monii\\Deal\\": "src", "Monii\\Deal\\resources": "resources" } } classpath:Monii/Deal/resources/mapping.yml => resources/mapping.yml classpath:Monii/Deal/resources/mapping.yml => vendor/monii/deal/resources/mapping.yml
66. Proposed to PHP-FIG
67. [Crickets.] — PHP-FIG
69. PSR-4 only cares about classes
70. Puli the future of PHP package development
72. HTTP Layer
73. Stack A convention for composing HttpKernelInterface middleware
74. Stack's Goal: Being able to write framework agnostic code at the HTTP layer
75. Limited to the Symfony Ecosystem
76. PSR-7 HTTP Message Interfaces
77. PSR-7 = HttpFoundation
78. One Year
79. Problem: No standard way to write PSR-7 middleware.
80. PSR-15 HTTP Middleware
81. PSR-7 = HttpFoundation PSR-15 = HttpKernel*
82. PSR-7 + PSR-15 = Stack's Vision. Realized.
83. Problem: In many cases it is hard to write PSR-7 code that is not tied to an implementation.
84. PSR-17 HTTP Factories
86. Purist vs Pragmatist
87. Closed Source
88. Will you actually reuse it?
89. Will you ever actually change frameworks?
90. Open Source
91. A lot of potential users from many potential frameworks
93. Your model may always be influenced by your ORM Accept it
94. Start simple Move business logic out of the glue's namespace
95. Think about the code you write directly into a glue package It can lead to better design
96. Consider creating separate packages for business logic and glue layers Only if it brings real value!
97. Try Puli Especially if you have non-code resources that need to be referenced
98. Consider your goals
99. Thanks! beau.io • @beausimensen thatpodcast.io • @thatpodcast
101. Engaging PHP-FIG was AWESOME (but very very very very exhausting)
102. PSR-0 Resource Locator (my experiment)
103. PSR-4 (getting involved)
104. Puli (something awesome)
105. Stack (my experiment)
106. PSR-7 (getting involved AND something awesome!)
107. I'm nobody
108. I'm just like you
109. Get involved :)