Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Rethinking the Client vs. Server Rendering Debate

Rethinking the Client vs. Server Rendering Debate

Given at MahattanJS

Rebecca Miller-Webster

March 19, 2014

More Decks by Rebecca Miller-Webster

Other Decks in Technology


  1. Server JavaScript MVC - Ember, Backbone, Angular etc JavaScript templates

    - Mustache, Underscore, etc jQuery + DOM manipulation w/ JSON Client Full page rendering; full page refresh Turbolinks PJAX jQuery + DOM manipulation Server returns HTML Server returns JSON
  2. Server Fast! Clear conventions Organization and Structure Reusable components Good

    UX for basic CRUD Easier to test Client Fast! Easier to cache Always show canonical data Less client/server code duplication Easier to test
  3. Real World == Hybrid HTML fragment inserted into DOM JS

    MVC model for JS component Single-page full MVC on some pages Per feature
  4. Solve YOUR Problem What’s the problem your trying to solve?

    Priority Timing How does this fit in with goals of the company?
  5. Right Tool for the Job Data: authority; present in multiple

    ways on the same page; reads vs. writes; size; store and respond to state Rendering: how much; single or many pages; need to display on-load; complexity; presentation based on state UX: importance of page load; user expectations; interactivity; devices; security
  6. Right Tools for your Team What’s your existing tools, conventions.

    organization? What tools do your people know? Time for spike and knowledge transfer? What do people want?