Building modern web applications. Single Responsibility Principle applied

Slides from my talk from GeeCON 2014. Slightly modified version comparing to one from 4Developers conf.

Transcript

1. Building modern web apps Single Responsibility Principle applied
2. Michal Ostruszka @mostruszka | michalostruszka.pl both-ends developer I crafting web applications
3. What not to expect? / code samples / frameworks / benchmarks / etc @mostruszka / #geecon
4. Here be dragons / old times, good times? / what projects need / how to / toolbox / not all is well / profits @mostruszka / #geecon
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 / #geecon
6. JavaScript all the things! @mostruszka / #geecon
7. Web app business logic AND view logic @mostruszka / #geecon
8. High coupling presentation business logic @mostruszka / #geecon
9. Shotgun surgery deployment risk @mostruszka / #geecon
10. Backend devs doing frontend @mostruszka / #geecon
11. Backend devs doing frontend / architecture / standards & browser support / performance @mostruszka / #geecon
12. Project needs / user experience / good performance / standards & browser support / maintainability / minimal-risk deployments @mostruszka / #geecon
13. Answer apply SRP on app level! @mostruszka / #geecon
14. Built by experts both apps built by highly-skilled teams @mostruszka / #geecon
15. Unlearn what you have learned you must @mostruszka / #geecon
16. 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 / #geecon
17. Source separation isolate frontend code @mostruszka / #geecon
18. Deployment isolation static stuff is static *.html *.js *.css *.png *.java *.rb *.scala *.php @mostruszka / #geecon
19. Need one build? build frontend as one of build steps @mostruszka / #geecon
20. Benefits right tools for the job @mostruszka / #geecon
21. Build toolbox for frontend / grunt, gulp / yeoman, lineman / make, ant + tons of extensions @mostruszka / #geecon
22. Backend / web as a transport layer only / micro web-frameworks / auto-documenting API / JSON standards @mostruszka / #geecon
23. One SPA fits all? not so fast, cowboy / SEO, indexing / Twitter’s time to first tweet / view-heavy apps / additional code to maintain @mostruszka / #geecon
24. node.js to the rescue? @mostruszka / #geecon
25. 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 / #geecon
26. backend / focus on business logic & core / keep well defined boundary / no more JS nightmares / independent development cycle Happy end @mostruszka / #geecon
27. frontend / focus on client logic & view / use well-defined API / deliver great user experience / use right tools / drive design, automate, test Happy end @mostruszka / #geecon
28. questions? .finish(now) @mostruszka / #geecon
29. 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 @mostruszka / #geecon