In my point of view: SPA is to solve server's scalability that before serverless and CDNnetwork prospect. But SPA still solve server's scalability for medium company.
Pro:
Good to running rendering in javascript client side, server take less time and resource for SSR. (10k client probably take your server a huge slow down)
Able to horizontal scaling
SPA is good if you using preact if you are medium, also using react with less libraries probably go to hooks and prevent introduce too much of different code structure than general public. Furthermore a boilerplate(create-react app alternative) to make all the web components together(react should be produce web component in heavy build way too?)
Cons:
Javascript is bad, noscript is good, but that the issue, almost everyone dependent on it.
We have gone down the road, as the cost of cloud computing is high, rely on server rendering is no a way, except SSR on CDN. That is passing the cost to user.
The problem of the big bundle size is the code splitting is not mature and the optimization is no superb now. Not as good as hand tuned old HTML5, CSS3, Javascript, because automation is just started
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
In my point of view: SPA is to solve server's scalability that before serverless and CDNnetwork prospect. But SPA still solve server's scalability for medium company.
Pro:
Cons: