Building modern web applications. Single Responsibility Principle applied

Slides from my talk I gave on 4Developers conference

Transcript

1. Building modern web apps Single Responsibility Principle applied Michal Ostruszka | @mostruszka
2. Michal Ostruszka @mostruszka | michalostruszka.pl both-ends developer at SoftwareMill I crafting web applications
3. Roadmap / old times, good times? / what projects need / how to / toolbox / not all is well / profits @mostruszka / #4developers
4. JavaScript all the things! @mostruszka / #4developers
5. Single Responsibility do you speak it? In object-oriented programming, the Single Responsibility Principle states that every class should have a single responsibility, and that responsibility should be entirely encapsulated by the class. All its services should be narrowly aligned with that responsibility. @mostruszka / #4developers
6. All in 1 business logic AND view logic @mostruszka / #4developers
7. High coupling presentation&business @mostruszka / #4developers
8. Shotgun surgery deployment risk @mostruszka / #4developers
9. Backend devs doing frontend @mostruszka / #4developers
10. Backend devs doing frontend / architecture / standards & browser support / performance @mostruszka / #4developers
11. Project needs / user experience / good performance / standards & browser support / maintainability / minimal-risk deployments @mostruszka / #4developers
12. Solution? apply SRP on app level @mostruszka / #4developers
13. Built by experts both apps built by highly-skilled teams @mostruszka / #4developers
14. Unlearn what you have learned you must @mostruszka / #4developers
15. API JSON-based view-less server browser as API client GET /api/users HTTP/1.1 Host: example.com Accept: application/json HTTP/1.1 200 OK Content-Type: application/json {"foo": "bar"} @mostruszka / #4developers
16. Source separation separate frontend code @mostruszka / #4developers
17. Deployment isolation static stuff is static *.html *.js *.css *.png *.java *.rb *.scala *.php @mostruszka / #4developers
18. Need one build? build frontend as one of build steps @mostruszka / #4developers
19. Possibilities? right tools for the job @mostruszka / #4developers
20. Build toolbox for frontend / grunt, gulp / yeoman, lineman / make, ant + tons of extensions @mostruszka / #4developers
21. Backend / web as a transport layer only / micro web-frameworks / auto-documenting API / JSON standards @mostruszka / #4developers
22. One SPA fits all? not so fast, cowboy / SEO, indexing / Twitter’s time to first tweet / view-heavy apps / additional code to maintain @mostruszka / #4developers
23. node.js to the rescue? @mostruszka / #4developers
24. node.js / middle layer / view server by JS devs / talks to backend API http://www.nczonline.net/blog/2013/10/07/node-js-and-the-new-web-front-end/ @mostruszka / #4developers
25. backend / focus on business logic & core / keep well defined boundary / no more JS nightmares / independent development cycle Happy end @mostruszka / #4developers
26. frontend / focus on client logic & view / use well-defined API / deliver great user experience / use right tools / drive design, automate, test Happy end @mostruszka / #4developers
27. questions? .finish(now) @mostruszka / #4developers
28. https://www.flickr.com/photos/nhoulihan/3560187593/ https://www.flickr.com/photos/notbrucelee/7219422352/ http://www.sapdesignguild.org/editions/edition1/walo1.asp http://www.quickmeme.com/meme/35pvym https://www.flickr.com/photos/matkalla/3990633574/ https://www.flickr.com/photos/ross/4368015/ https://www.flickr.com/photos/nostri-imago/3461159301 http://www.keepcalm-o-matic.co.uk/p/keep-calm-and-call-jason-bourne-2/ http://kaminopedia.wikia.com/wiki/Yoda Credits