Framework Agnostic packages

Talk at PHPlx Lisbon about framework agnostic packages. How to create them, when and why.

Transcript

1. Build Framework Agnostic packages 29-10-2014 PHPLX Miguel Loureiro
2. Who am I ? Miguel Loureiro
3. • Software Engineer @ Uniplaces Who am I ? Miguel Loureiro
4. What is UX design? • Software Engineer @ Uniplaces • Entrepreneur Who am I ? Miguel Loureiro
5. What is UX design? • Software Engineer @ Uniplaces • Entrepreneur • Playing with PHP since 2010 Who am I ? Miguel Loureiro
6. What is UX design? • Software Engineer @ Uniplaces • Entrepreneur • Playing with PHP since 2010 • Web stack enthusiast Who am I ? Miguel Loureiro
7. Seriously, what is UX design? What is UX design? • Software Engineer @ Uniplaces • Entrepreneur • Playing with PHP since 2010 • Web stack enthusiast • Sports addict Who am I ? Miguel Loureiro
8. What we’ve been doing wrong. (before composer)
9. User needs Business goals SCENARIO 1. You have a framework of choice that tries to make everything you need.
10. SCENARIO 1. You have a framework of choice that tries to make everything you need. 2. Of course there’s something the framework doesn’t do.
11. SCENARIO 1. You have a framework of choice that tries to make everything you need. 2. Of course there’s something the framework doesn’t do. 3. You search and find a bundle/extension whatever… great!
12. User needs Business goals Technical constraints SCENARIO 1. You have a framework of choice that tries to make everything you need. 2. Of course there’s something the framework doesn’t do. 3. You search and find a bundle/extension whatever… great! 4. A ‘better’ framework appears, all your bundles/extensions don’t work anymore.
13. User needs Business goals SCENARIO 1. You have a framework of choice that tries to make everything you need. 2. Of course there’s something the framework doesn’t do. 3. You search and find a bundle/extension whatever… great! 4. A ‘better’ framework appears, all your bundles/extensions don’t work anymore. 5. Those bundles/extensions are forked to work in different frameworks.
14. User needs Business goals SCENARIO 1. You have a framework of choice that tries to make everything you need. 2. Of course there’s something the framework doesn’t do. 3. You search and find a bundle/extension whatever… great! 4. A ‘better’ framework appears, all your bundles/extensions don’t work anymore. 5. Those bundles/extensions are forked to work in different frameworks. 6. Now there’s a need to maintain N different forks of the extension.
15. User needs Business goals SCENARIO 1. You have a framework of choice that tries to make everything you need. 2. Of course there’s something the framework doesn’t do. 3. You search and find a bundle/extension whatever… great! 4. A ‘better’ framework appears, all your bundles/extensions don’t work anymore. 5. Those bundles/extensions are forked to work in different frameworks. 6. Now there’s a need to maintain N different forks of the extension. 7. Bug fixes are not global
16. User needs TOTAL MESS
17. give… us… interoperability
19. So, everything should be ok now. kkthxbye, end of story!
20. NOT! :(
21. People are doing packages dependent on frameworks
22. How to solve this ?
23. Logger
24. The fastest implementation
25. • Session is hardcoded so you can’t mock the Session class The fastest implementation
26. The fastest implementation • Session is hardcoded so you can’t mock the Session class • Framework dependent
27. Lets use some dependency injection ! :)
28. A better implementation
29. A better implementation • Still depends on Laravel’s session class. (Illuminate\Session\Store)
30. A better implementation • Still depends on Laravel’s session class. (Illuminate\Session\Store) • Why do we care that it comes from a session?
31. A better implementation • Still depends on Laravel’s session class. (Illuminate\Session\Store) • Why do we care that it comes from a session? • Why do we care that it logs to a file ?
32. Find the right abstractions
33. The right way
34. Start native
35. UserAudit Implementation Output Implementation
36. Now, the UserAudit framework implementation
37. Laravel’s UserAudit Implementation
38. Summing up
39. Find your abstractions
40. Follow S.O.L.I.D. principles
41. Start native
42. Implement for your framework after
43. Everyone’s happy :)
44. Questions ?