In the past few years, 'client-side' web applications have become popular. A common approach nowadays is to have the backend as thin as possible, mostly exposing an API for the client-side Javascript app to consume.What I'm interested in is not the advantages of this approach, as this seems to be the preffered approach today and its pros have been discussed on this site.I'm interested in the advantages of the more traditional, backend-based approach. Where the templating and routing of pages happens on the backend, and the frontend logic is thin.Please note, that this question refers to standard 'CRUD' applications, not to specialized video-editing software or programs executing intense algorithms (this kind of computation obviously needs to happen on the backend).I'm referring to the advantages of a backend architecture for your 'typical web app'.
What are the advantages of a 'traditional' 'backend' architecture for a standard CRUD app?
architecture;web;front end;backend