How Do We Decide to Create a Symfony Component?
summary
Explains how to decide whether to create a new Symfony component by describing the decision criteria and trade-offs involved. Covers concrete factors such as project modularity, reuse potential, maintenance cost, and integration with the Symfony ecosystem to guide when extracting functionality into a standalone component makes sense.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:29Symfony context and impact
- 5:07History of first components
- 8:39Creation for specific needs
- 14:15Modern component evolution
- 23:13Component debates and controversies
- 32:01Creation motivations and principles
- 37:35Packaging and dependencies
- 40:21Conclusion
related talks
35mThe Symfony Workflow Component Is Graphically Great!
44mQ&A session
02h 27mSymfony 4 best practices (Part 1)
01h 00mStandardization, the Symfony Way
48mDeveloping Symfony applications in 2023
41mMinimal Symfony in real life
34mSymfony 4: A new Way to develop Applications
34mGetting the most out of Symfony4