SPA Vs Traditional Web

There are 3 general approaches to building web applications today:

• traditional web applications that perform most of the application logic on the server,
• and single page applications (SPAs) that perform most of the user interface logic in a web browser, communicating with the web server primarily using web APIs.
• A hybrid approach is also possible, the simplest being host one or more rich SPA-like sub-applications within a larger traditional web application.

When to choose traditional web apps

1. If intent is to show read only contents and simple client side requirements.
2. Need separate url for each contents (like blogs) so that search engine optimization can be done.
3. Application need to support in browsers without javascript support.
4. Your team is not aware of javascript/typescript.

When to choose SPA

1. Need rich and fast user interface (fetching data in background)

2. When you need more responsive (because full page re-load is totally avoided)

3. SPAs can be designed to run in a disconnected mode, making updates to a client-side model that are eventually synchronized back to the server once a connection is re-established

3. Your team should be competent in writing modern JavaScript using a SPA framework like Angular.