Chapter 1. Introducing Aurelia
Figure 1.1. Aurelia maintains a separation of concerns between the structure, style, and behavior of pages. This allows for these pieces to be worked on independently, and by the person best suited for the job.
Figure 1.2. Server-side applications retrieve the entire page load as one rendered resource from the server (in addition to any CSS and JavaScript that is typically loaded separately).
Figure 1.3. Full client-side SPA. An entire application is bundled and returned in one or two responses from the server and rendered in the browser. Subsequent AJAX requests completed to populate data that isn’t required in the initial page load.
Figure 1.4. Hybrid SPA approach. In this model, the main content parts of the site are done with the traditional server-side approach. The product list and blog endpoints return the relevant HTML rendered from the server. But you then create multiple smaller SPAs to add rich interaction to the parts of the site that need it, such as the store.
Figure 1.5. In this server-side-rendered SPA model, the initial page render is done on the server side, but once the application has been loaded into the browser, the SPA framework takes over, and subsequent interactions are done on the client side.
Figure 1.6. A high-level map of the Aurelia framework. At its core, Aurelia is an MV* framework.