Page & Bundle
Visualforce pages (and Visualforce additives, but permits’s set those apart for now) are saved on Salesforce as a single entity, an ApexPage. When you use Salesforce Extensions for Visual Studio Code or some other tool to copy your Visualforce pages to your local garage to work on them.
Although your web page might have dependencies on other artifacts, like an Apex controller or extension, static assets, and so forth, they may become independent from the page. Your web page references them, however doesn’t encompass them.
An Aura thing has greater to it than a code artifact plus metadata, with up to eight code artifacts plus metadata these days (9 general). For this cause, a man or woman aspect is stored in a package deal that consists of sources. This package is represented as a folder of files when you store it in your nearby store.
Don't forget to check out: 8 Foolproof Steps to Salesforce Classic to Lightning Migration
Server-Side & Client-Side
Page by Page & Single Page Application
When you design a conventional Visualforce-primarily based app, you normally create a fixed of pages, and users of the app navigate through moving from one page to every other page. You start on a listing view page, click on a view link to visit a file view page, click an edit button to visit an edit report web page, and so on.
Check out another amazing blog by Anjali here: An Ultimate Guide to Salesforce Flow Builder User Interface
Instead of navigating from page to page, customers navigate from state to nation. A nation represents a method that your app is currently in. The listing view country, the view report nation, and so on.
The SPA knows which additives to load for every nation, and those additives realize a way to draw or render themselves.