Symfony 4 internals

Tobias Nyholm (15.Sep.2018 at 14:30, 50 min)
Talk at Cascadia PHP (English - US)

Rating: 5 of 5

Symfony is a request and response framework. But what about all that magic that happens around your code? Why isn’t autowring slowing things down? And how is it that Symfony components can be so decoupled but sill play so well together?

I will show you the Symfony internals and its architecture.

This talk will go over the architecture of Symfony. We will follow the request and the response paths throw the framework. We will do some stops at the components that are more awesome than others.

This talk is perfect for you who been working with Symfony or Laravel before. But if you never touched a framework before, don't worry. You will still learn a lot from this talk.

Who are you?

Claim talk

Talk claims have been moved to the new Joind.in site.

Please login to the new site to claim your talk

Want to comment on this talk? Log in or create a new account or comment anonymously

Write a comment

 
Please note: you are not logged in and will be posting anonymously!
= one plus five

Comments

Rating: 5 of 5

16.Sep.2018 at 02:07 by Demin Yin (4 comments) via Web2 LIVE

Great talk! Sample code used in the slides are very well organized to guide the audience to get familiar with Symfony workflow easily. I also like the way how you used breakpoints and other features in Phpstorm to demo the code. The best talk I have seen for developers who what to know how Symfony (and Laravel) applications work in detail. Thanks

Rating: 5 of 5

19.Sep.2018 at 14:01 by A3020 (7 comments) via Web2 LIVE

First of all, I don't know Tobias, although we shook hands later on. I liked his talk. It was in-depth and gave a great overview of how a modern application could bootstrap / run. The talk was well prepared and the code examples made sense. He even did live step-through 'debugging' at the end. That went well. In the beginning of the presentation, Tobias started his example with a switch statement. Then multiple libraries / dependencies were added, one after another. With each step I thought, ok, will we now get rid of the switch statement? I think the talk was not really about solving a problem (aka, the switch). It felt more like a reversed showcase of a solution to me. But, nonetheless, it was well presented, well prepared, and just very interesting. Well done!

© Joind.in 2018