With all the trending front-end frameworks being discussed these days, like Angular, ReactJs, VueJs, EmberJs, which most of them make our life easier to make Single Page Application, seems like the bigger question of, “Should we even build our web app, a SPA or not” is being ignored

I believe it is important to understand that traditional web application approach might be still a better approach in some cases, so I decided to write about these two approaches and their use-cases.

Today, there are two general approaches when you build a web applications: traditional web apps, that means we do most of the logic on the server side, and single page applications (SPAs) that most of the UI code is in the browser and we make some API calls for CRUD operations.

Here are the summary of each approach and use cases for each one as a quick reference:

Traditional web applications use cases

Our web application is supposed to run on browsers that does not support JavaSctipt! (This is very important)

Our web application is very simple and is mostly read only stuff.

Resources (Developers) in our team aren’t familiar with JavaScript or TypeScript or Front-end development.

Single Page Application use cases