Downloaded 149 times
Uploaded byLars Jankowfsky
Why Architecture in Web Development matters
The document provides insights from Lars Jankowfsky on effective software architecture, emphasizing principles such as separation of concerns, avoiding complexity, and implementing modular structures. It discusses the advantages and challenges of different architectural practices, including layered architecture and service-oriented architecture (SOA), and stresses the importance of maintaining clean code and conducting thorough testing. Key principles highlighted include the DRY principle, the necessity of avoiding business logic in controllers, and the benefits of using template engines.
Editor's Notes
- #16 strong dependency -> „co-dependency“
- #20 \"if you want to serialize to xml do not create \"toxml\" Method, instead pass $this to the XMLExporter\"
- #21 think in advance but don‘t think too complex before making any generalisation have at least two cases the more abstractions the easier you can change it later
- #22 nobody said it will be easy
- #23 tightrope walk
- #48 preparing fixtures/Mocks difficult
- #49 preparing fixtures/Mocks difficult
- #50 preparing fixtures/Mocks difficult
- #51 preparing fixtures/Mocks difficult
- #52 preparing fixtures/Mocks difficult
- #65 do not spread db calls through your code one function or object generates one „business“ result data access object
- #66 do not spread db calls through your code one function or object generates one „business“ result data access object
- #67 do not spread db calls through your code one function or object generates one „business“ result data access object
- #73 lazy loading ok in Ruby all Variables from controller are accessable.
- #74 lazy loading ok in Ruby all Variables from controller are accessable.
- #75 lazy loading ok in Ruby all Variables from controller are accessable.
- #76 Do not reinvent the wheel. Use frameworks
- #82 at least daily
- #83 test a single class do not touch database, network, (files) use mocks/stubs and provide fast feedback
- #84 test several classes test communication between classes/modules they test full components
- #85 test functionality from „outside“ often build from „user stories“ usually done with Selenium -> not only selenium example openapi