What frameworks can do for you – and what not (IPC14 SE)
0 likes901 views
The document discusses the capabilities and limitations of software frameworks, emphasizing that a framework alone does not guarantee a successful application. It highlights the importance of understanding features like ORM, security, and abstraction layers, while also pointing out that some frameworks can simplify development but may introduce complexities. Ultimately, it suggests balancing the benefits of frameworks with the need for greater flexibility when necessary, especially for non-trivial applications.
What frameworks can do for you – and what not (IPC14 SE)
- 1. What frameworks can do (and what not) Robert Lemke - TechDivision GmbH
- 2. TEXT HERE Robert Lemke ! 38 years old lives in Lübeck, Germany software architect at TechDivision TYPO3 Association co-founder TYPO3 Flow & TYPO3 Neos project founder 1 wife, 2 daughters, 1 espresso machine
- 3. Expectations. Promises. Features. Long Term Relationships.
- 4. What do you expect from your IDE?
- 5. What do you expect from a framework?
- 6. „Implement our company website. It must be based on TYPO3 CMS.”
- 7. A framework is no architecture.
- 8. A framework alone won’t make a great application.
- 9. Promises
- 12. „extensible”
- 13. „secure”
- 14. „PHP is fun again”
- 16. „based on another cool framework”
- 18. „… is right for you if you want to spend more time away from your computer”
- 19. Features
- 20. Speed
- 21. Frameworks add more layers of abstraction.
- 22. Abstraction layers slow down your application.
- 23. Without a framework, most likely, you will add these layers yourself.
- 24. Abstraction layers speed up your application.
- 30. speed doesn’t come for free.
- 31. Persistence
- 32. An ORM layer slows down your application and is less flexible.
- 33. An ORM layer can make your application less complex and respond faster.
- 34. keeps your domain model clean.
- 36. Don’t implement an ORM – it’s way too complex to get it right.
- 37. Do implement an ORM – you need to know the inner works.
- 38. Do you need an ORM?
- 39. A DBAL makes your application more portable.
- 40. Do you need a DBAL?
- 41. Used correctly, ORMs can be a blessing.
- 42. Security
- 43. A framework can make your application more secure.
- 44. Implementing cryptography algorithms on your own is wantonly negligent!
- 45. Implementing authentication and authorisation adapters is a whole project on its own.
- 46. Do you have the manpower and expertise?
- 47. Still, you are responsible for security.
- 48. You need to learn about security, no matter what.
- 49. Guidance
- 50. TYPO3FlowCodingGuidelinesononepage <?php namespaceAcmeTestPackage; /* * *ThisscriptbelongstotheTYPO3Flowpackage"Acme.TestPackage". * * * *Itisfreesoftware;youcanredistributeitand/ormodifyitunder * *thetermsoftheGNUGeneralPublicLicense,eitherversion3ofthe * *License,or(atyouroption)anylaterversion. * * * *TheTYPO3project-inspiringpeopletoshare! * * */ useAcmeTestPackageServiceFooGenerator; useTYPO3FlowAnnotationsasFlow; /** *Heregoesthedescriptionoftheclass.Itshouldexplainwhatthemain *purposeofthisclassis... * *@FlowScope(”singleton”) */ classUniverseAnalyzerextendsBaseClassimplementsSomeInterface{ /** *Someinjecteddependency * *@FlowInject *@varFooGenerator */ protected$someDependency=NULL; /** *ShowsifyouareaddictedtoTYPO3Flow * *@varboolean */ staticprotected$addictedToFlow=TRUE; /** *ShowsifyouareafanofTYPO3Flow * *@varboolean */ protected$fanOfFlow; /** *Agreatmethodwhichshowshowtoindentcontrolstructures. Descriptionoftheclass.Makeitas longasneeded,feelfreetoexplain howtouseit. Namespacestartswithvendorname followedbypackagekey(name)and subpartsasneeded UpperCamelCaseclassname.Class namesshouldbenouns. Inotherpackages,import AcmeTestPackageUniverseAnalyzer andrefertoitasUniverseAnalyer. Use@vartag.Optionaldescription goesinthefirstcommentline followedbyablankcommentline. Descriptionofthemethod.Makeit aslongasneeded. Methodnamesshouldbeverbs. Oneusestatementperline. Oneusestatementpernamespace. Orderstatementsalphabetically. Don'timportnamespacesunlessyou usethem. NoemptylinebetweenDocComment andclass,membervarormethod. Preferrelativenamespaces,unless FullyQualifiedNamespaceismore readable List@Flow*beforeothertags: @var,@param,@return,@throws, @api,@since,@deprecated Capturethejoyofcodingasyou createexcellentwebsolutions. Enjoycoding.EnjoyFlow. http://rlmk.me/flowcgl
- 52. 0 75 150 225 300 Security Speed MVC HTTP Templating i18n You will have to learn a lot … start working on business logic
- 53. … the question is: in which order? 0 100 200 300 40 Framework Security Speed MVC HTTP Templating i18n C64 E. start working on business logic
- 54. But hey, what about Agile?
- 55. Bottomline?
- 56. Frameworks offer a shortcut and many features right away.
- 57. Going framework-less gives you more flexibility.
- 58. Non-trivial applications will need a framework sooner or later.
- 59. Only start creating your own application-specific framework if you have the experience and resources.