Symfony without the framework bundle
summary
Argues that frameworks aren’t inherently slow and shows concrete steps: measure with a profiler, apply three rules — buy better hardware, cache everything using the Symfony Cache interface (with built‑in stampede protection), and run less code. Replaces full FrameworkBundle with a tiny middleware microframework and optional custom kernel using Symfony HttpKernel and components (Messenger, Workflow). Demonstrates redirect and geocoder services hitting ~10ms (claims under 15ms and even ~5ms possible) and explains keeping containers compiled plus using a long‑running PHP process instead of PHP‑FPM for extra gains.
AI-written summary · about
chapters (22)
- 0:00Intro
- 3:49What is a framework?
- 8:47Symfony is a community
- 9:03Symfony is an ecosystem a community
- 9:15Symfony is whatever we make
- 10:32Let's talk about performance
- 10:55Buy a better server
- 11:51Run less code
- 12:58More code = More "ticks"
- 14:44What is your application doing?
- 17:41Do we need HTTP?
- 18:09Messenger component?
- 18:54Doctrine or just PDO?
- 19:46Building a small application
- 20:10Workflow component
- 20:58Cache component
- 24:24Middleware pattern
- 27:45Custom kernel
- 30:44Too much boilerplate? Use the FrameworkBundle
- 32:33Improve performance
- 33:18Profile your application
- 38:31Remember
related talks
39mKeynote: Symfony without the Framework Bundle
48mBuilding Really Fast Applications
01h 01mDeep dive into Symfony 4 internals
40mDeep dive into Symfony 4 internals
41mMinimal Symfony in real life
57mEating spaghetti with Symfony
01h 00mStandardization, the Symfony Way
34mSymfony 4: A new Way to develop Applications