Introducing the Angular router
In traditional web applications, when we wanted to change from one view to another, we needed to request a new page from the server. The browser would create a URL for the view and send it to the server. As soon as a response was received from the server, the browser would reload the page. This was a process that resulted in round trip time delays and a bad user experience for our applications:
Figure 7.1 – Traditional web applications
Modern web applications that use a JavaScript framework such as Angular follow a different approach. They handle changes between views or components on the client side without bothering the server. They contact the server only once during bootstrapping to get the main index.html file. Any subsequent URL changes are intercepted and handled by the router on the client. These types of applications are called Single-Page Applications (SPA) because they do not cause a full reload of a page...