Design pattern in Symfony2 - Nanos gigantium humeris insidentes
27 likes31,965 views
This document discusses various design patterns used within the Symfony framework such as the Front Controller pattern, Decorator pattern, Dependency Injection, and others. It also discusses anti-patterns to avoid like over-engineering, overuse of patterns, big ball of mud, and reinventing the wheel. Throughout the document there is an emphasis on decoupling code and avoiding tightly coupled spaghetti code.
More Related Content
What's hot (19)
Similar to Design pattern in Symfony2 - Nanos gigantium humeris insidentes (20)
More from Giulio De Donato (13)
Recently uploaded (20)
Design pattern in Symfony2 - Nanos gigantium humeris insidentes
- 1. Nanos gigantium humeris insidentes DESIGN PATTERN INSIDE SYMFONY2
- 2. GIANTS
- 3. liurrrgio GIULIO DE DONATO GIORGIO CEFARO @liuggio @giorrrgio
- 5. DESIGN PATTERN A solution of a problem in a context James O. Coplien (1994)
- 6. DESIGN PATTERN “ For me a pattern is primarily a way to chunk up advice about a topic “
- 7. #1
- 8. FRONT CONTROLLER INTENT: A controller that handles all requests for a Web site
- 10. FRONT CONTROLLER ... and ? web/app.php
- 11. INTENT: DECORATOR Attach additional responsibilities to an object dynamically. Decorators provide a flexible alternative to subclassing for extending functionality.
- 14. KERNEL AND SERVICE CONTAINER SymfonyComponentHttpKernelKernel
- 16. INVERSION OF CONTROL INTENT: Inversion of control is a style of software construction where reusable code controls the execution of problem-specific code
- 18. “ Inversion of control is a common characteristic of frameworks, so saying that these lightweight containers are special because they use inversion of control is like saying my car is special because it has wheels.”
- 19. INVERSION OF CONTROL HOLLYWOOD PRINCIPLE: “ DON’T CALL US WE’LL CALL YOU ”
- 21. PICO CONTAINER DEFINITION: "Dependency Injection is where components are given their dependencies through their constructors, methods, or directly into fields."
- 22. Dependency injection allows the removal of hard-coded dependencies and makes it possible to change them, whether at run-time or compiletime.
- 23. INJECTING A TRANSPORT INSIDE A MAILER
- 24. - FIGHT OF THE DAY - SERVICE CONTAINER vs DEPENDENCY INJECTION
- 25. INVERSION OF CONTROL INTENT: DECOUPLE DECOUPL DECOUPLE DECOUPLE DECOUPLE DECOUPLE DECOUPLE DECOUPLE DECOUPLE DECOUPLE
- 26. DEPENDENCY INJECTION AND FRAMEWORKS DI ?? Grafico con spaghetti, infermiera che fa la puntura, lista della spesa per l'antipattern service locator, qualcosa di galattico per l'enhanced injection (tipo pulp fiction) http://www.loosecouplings.com/2011/01/dependency-injection-using-di-container.html DIC
- 27. FACTORY METHOD INTENT: Define an interface for creating an object, but let subclasses decide which class to instantiate. Factory Method lets a class defer instantiation to subclasses.
- 28. FACTORY METHOD - DO IT WITH THE DIC
- 29. ABSTRACT FACTORY INTENT: Provide an interface for creating families of related or dependent objects without specifying their concrete classes.
- 30. ABSTRACT FACTORY - SecurityFactoryInterface SymfonyBundleSecurityBundleDependencyInjectionSecurityFactorySecurityFactoryInterface
- 31. INTENT: BUILDER Separate the construction of a complex object from its representation so that the same construction process can create different representations.
- 33. FORM BUILDER
- 34. PROXY INTENT: Provide a surrogate or placeholder for another object to control access to it.
- 36. MEDIATOR INTENT: Define an object that encapsulates how a set of objects interact. Mediator promotes loose coupling by keeping objects from referring to each other explicitly, and it lets you vary their interaction independently.
- 37. ner file Kernel :: REQUEST rLi ste gm ent Fra ste Li on ssi Se Pro List ene r MEDIATOR er ten rLis te Rou ner EVENT DISPATCHER Loca leLis tene r all ew Fir
- 38. STRATEGY aka POLICY INTENT: Defines a family of algorithms, encapsulate each one, and make them interchangeable. Strategy lets the algorithm vary independently from clients that use it.
- 41. DATA MAPPER INTENT: A layer of Mappers that moves data between objects and a database while keeping them independent of each other and the mapper itself.
- 42. VISITOR INTENT: Represent an operation to be performed on the elements of an object structure. Visitor lets you define a new operation without changing the classes of the elements on which it operates.
- 45. AbstractionInversion, AccidentalComplexity, AccidentalInclusion, AddingEpicycles, AlcoholFueledDevelopment, AmbiguousViewpoint, AnalogyBreakdownAntiPattern, AnalysisParalysis, AnAthena, AppointedTeam, ArchitectsDontCode, ArchitectsPlayGolf, ArchitectureAsRequirements, ArchitectureByImplication, AsynchronousUnitTesting, AutogeneratedStovepipeAntiPattern, BandAid, BearTrap?, BigBallOfMud, BlameStorming, BlowhardJamboree, BoatAnchor, CargoCult, CarParkSyndrome, CascadingDialogBoxesAntiPattern, ContinuousObsolescence, ConfusionOfObjectives, ControlFreak, CopyAndPasteProgramming, CornCob, CoverYourAssets, CreepingFeaturitis, CrciCards, CryptoCracy, DeadEnd, DeathByPlanning, DecisionByArithmetic, DesignByCommittee, DesignForTheSakeOfDesign., DiscordantRewardMechanisms, DoerAndKnower, DryWaterhole, EgalitarianCompensation, EmailIsDangerous, EmperorsNewClothes, EmpireBuilding, ExceptionFunnel, FalseEconomy, FalseSurrogateEndpoint, FearOfSuccess, FireDrill, FloatingPointCurrency, FloatingPointFractions, FoolTrap, FunctionalDecomposition, FungibleTeams, FungibleProjectManager, GeographicallyDistributedDevelopment, GiveMeEstimatesNow, GlassWall, GodClass, GoldenHammer, GroundHogDayProject, HalfDoneIsEnough, HeirApparent, HeroCulture, HiddenRequirements, IdiotProofProcess., IfItIsWorkingDontChange, IfOk, InappropriateTechnicalObjective, InputKludge, ItsAnOperatorProblem, JobKeeper, JumbleAntipattern, JunkyardCoding, KillTwoBirdsWithOneStone, KitchenSinkDesign, LavaFlow, LeadingRequest, MagicContainer, ManagerControlsProcess, MushroomManagement, Nationalism, NetNegativeProducingProgrammer, NotInventedHere, NotTheAppropriateProtocol, NullFlag, OverGeneralizationOfBusinessLogic, OverUseOfPatterns, PathOfLeastResistance, ParsingHtmlWithRegex, PassingNullsToConstructors, PlugCompatibleInterchangeableEngineers, PoliticsOrientedArchitecture, PolterGeists, ReinventingTheWheel, ReinventTheWheel, RollYourOwnDatabase, RequirementsTossedOverTheWall, RubeGoldbergMachine, ScapeGoat, SeagullManagement, SecretSociety, SellingaProductYouCantRealize, ShootTheMessenger, SingleFunctionExitPoint, SmokeAndMirrors, SoftwareMerger, SpaghettiCode, SpecifyNothing, StandingOnTheShouldersOfMidgets, StovepipeAntiPattern, StringWithoutLength, SumoMarriage, SweepItUnderTheRugAntiPattern, SwissArmyKnife, ThatsNotReallyAnIssue, TheBlob, TheCustomersAreIdiots, TheGrandOldDukeOfYork, TheProcessIsTheDeliverable, TheyUnderstoodMe, ThrownOverTheWall, TowerOfVoodoo, TrainTheTrainer, UntestedButFinished, VendorLockIn, ViewgraphEngineering, VietnamWarAntiPattern, VoodooChickenCoding, WalkingThroughaMineField, WarmBodies, WeAreIdiots, WolfTicket, YetAnotherMeetingWillSolveIt, YetAnotherThreadWillSolveIt, ANTI-PATTERN
- 46. DESIGN FOR THE SAKE OF DESIGN “I only ship the perfection" ANTI PATTERNS
- 47. OVER ENGINEERING OVERUSE OF PATTERNS ANTI PATTERNS
- 48. THE BLOB BIG BALL OF MUD ANTI PATTERNS
- 49. GLOBALIZING STANDING ON THE SHOULDER OF THE MIDGETS ANTI PATTERNS
- 50. REINVENTING THE WHEEL NIH SYNDROME ANTI PATTERNS
- 52. code spends more time being read and maintained than being created
- 53. DECOUPLE
- 54. DECOUPLE
- 55. DECOUPLE.
- 56. GOOD QUESTIONS ARE BETTER THAN GOOD ANSWERS