4 ms·
One of the under appreciated reason why spa took off is it exploits the lower cdn cost. Things that generate html on the server side need to pay for the higher
by pyrolistical 2y ago
One of the under appreciated reason why spa took off is it exploits the lower cdn cost.
Things that generate html on the server side need to pay for the higher bandwidth costs that are hard to cache well.
In the other hand with spa, a well configured cdn can have a short ttl on index.html and cache the unique per deployment js bundles forever.
The only server bandwidth cost is the actual api data
- hasanhaja 2y agoI don't think so. You can still generate a significant amount of your static HTML at build before pushing that to a CDN, and load dynamic content using JS; JAM Stack.