title: How much "single paged" a complex application can be?
body: <p>I'm working on a quite a large application with several sub modules. Each of the sub module can be of complex functionality with many panels and UI components. I had done smaller scale projects before as a single page application, but this time worried on the fact that my DOM will not be refreshed for a long time if user keeps on working across many modules.</p>
  
  <p>When I analyze how Facebook operates, I see it works as a single page app most of the time. But time to time it refreshes the whole DOM with an action of the user (apparently it is random OR based on user activity count). </p>
  
  <p>Is their any pattern or best practice on how one might create such large applications as single page, without compromising DOM performance?</p>
  
  <p>(I'm NOT looking for coding techniques to keep the memory foot print low.. but for a design approach for the total application)</p>