Prendre un Café

L'espace d'expression de Nicolas Perriault

Aller au contenu | Aller au menu | Aller à la recherche

« YAML Brush for the SyntaxHighlighter Javascript | Optimize your Doctrine Workflow with Specialized »

30 Symfony Best Practices, the slides from my talk at SymfonyDay Cologne '09

Par NiKo le vendredi 4 septembre 2009, 20:50 - Dev - Lien permanent - 6 commentaires - Commenter

Tags :

Hey there, it’s been a while, huh?

Today I gave a talk about Symfony best practices at the Symfony Day event in Cologne, Germany; you can get the slides on slideshare or directly browse them below:

The Symfony Day event has been purely awesomely incredibly well organized, many kudos and thanks to Interlutions and to all the attendees. You’re all great people. Thanks.

6 commentaires (Ajouter un commentaire)

1. Le samedi 5 septembre 2009, 07:11 par vince

Cool it happened all that good !
Having a look a you slides work

2. Le samedi 5 septembre 2009, 10:16 par Eric Bartels

It was a very nice presentation! I really really like #0!

3. Le samedi 5 septembre 2009, 12:50 par Hugo

Thanks for sharing this N1K0

4. Le lundi 7 septembre 2009, 10:39 par Sylvio

Thanks a lot for the slideshow and Bravo for the event !

I have some question :
- Why "avoid using cache" ? do you talk about cache in prod env for projects ? Cache is very powerfull and it is a great feature of SF ? Maybe I don't understand the context of the slide.
- Why not store objects in user session ? It is too heavy ? For some project I use or design some special class (like sfShoppingCart and currentOrder) for storing some structured data in user session, is it a bad practice ?

5. Le lundi 7 septembre 2009, 13:48 par NiKo

Sylvio:

> Why "avoid using cache" ? do you talk about cache in prod env for projects ? Cache is very powerfull and it is a great feature of SF ?

Because cache invalidation rules are a true nightmare to conceive and maintain. You will save a lot of time (which is basically money) and aspirine without having to deal with that.

> Why not store objects in user session ? It is too heavy ?

Yes. Session data are stored on the server side (some could use crypted cookie storage, but with very little amount of data), and these data are written on the filesystem, or in a database, or maybe in memcache. But a serialized Doctrine object for instance is HUGE. So you'll quickly encounter problems if you have to make your application scaling.

6. Le vendredi 11 septembre 2009, 22:53 par Sid