Building modern web apps Single Responsibility Principle applied 

Michal Ostruszka @mostruszka | michalostruszka.pl both-ends developer I crafting web applications 

What not to expect? / code samples / frameworks / benchmarks / etc @mostruszka / #geecon 

Here be dragons / old times, good times? / what projects need / how to / toolbox / not all is well / profits @mostruszka / #geecon 

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 

JavaScript all the things! @mostruszka / #geecon 

Web app business logic AND view logic @mostruszka / #geecon 

High coupling presentation business logic @mostruszka / #geecon 

Shotgun surgery deployment risk @mostruszka / #geecon 

Backend devs doing frontend @mostruszka / #geecon 

Backend devs doing frontend / architecture / standards & browser support / performance @mostruszka / #geecon 

Project needs / user experience / good performance / standards & browser support / maintainability / minimal-risk deployments @mostruszka / #geecon 

Answer apply SRP on app level! @mostruszka / #geecon 

Built by experts both apps built by highly-skilled teams @mostruszka / #geecon 

Unlearn what you have learned you must @mostruszka / #geecon 

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 

Source separation isolate frontend code @mostruszka / #geecon 

Deployment isolation static stuff is static *.html *.js *.css *.png *.java *.rb *.scala *.php @mostruszka / #geecon 

Need one build? build frontend as one of build steps @mostruszka / #geecon 

Benefits right tools for the job @mostruszka / #geecon 

Build toolbox for frontend / grunt, gulp / yeoman, lineman / make, ant + tons of extensions @mostruszka / #geecon 

Backend / web as a transport layer only / micro web-frameworks / auto-documenting API / JSON standards @mostruszka / #geecon 

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 

node.js to the rescue? @mostruszka / #geecon 

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 

backend / focus on business logic & core / keep well defined boundary / no more JS nightmares / independent development cycle Happy end @mostruszka / #geecon 

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 

questions? .finish(now) @mostruszka / #geecon 

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