SPA (Single Page Application)
SPA consists of a single page and has the advantage of being simple to deploy and providing a user experience similar to native apps compared to existing server-side rendering. SPA basically download all static resources required for web applications only once upon initial access. When requesting a new page, JSON delivers only the data needed to update the page, thereby reducing overall traffic and updating only the changed parts without rendering the entire page again, providing a user experience similar to the native app.
Flaws of SPA
- The SPA downloads all static resources required for web applications only once upon initial access, so the initial operation speed is relatively slow. but, Considering the advantages of traffic reduction, speed, usability, and improved reactivity, it cannot be said to be a decisive disadvantage.
- SPA generally operate in the Client Side Rendering(CSR) method of the Javascript-based as asynchronous model rather than the Server Side Rendering(SSR) method. CSR receives data from a server through a data patch request and dynamically generates a page, but at this time, the URL of the browser address is not changed. This means that the user visit history cannot be managed, and it is also the cause of SEO issues. The SEO issue of SPA has always been a drawback. However, SPA frameworks such as React and Angular already have ability that support SSR, and modern browsers are known to solve SEO issues.
Footprints in Coding