Is server side routing the same as rendering server side / isomorphic javascript?

I am struggling to see the difference between server side routing and redirecting to it and server side rendering / isomorphic javascript. How different they are if they are different.

+3


source to share


1 answer


Universal (isomorphic) Javascript can execute on both client and server and share application state between the two parties. This means that the application uses the same rendering engine on the client and on the server. The point is that the client must continue to work from the place where the server finished its work.

Main advantages:

  • SEO
  • performance

On the other hand, we have the old way of communicating with SPA (Single Page Applications). It runs entirely in a browser and the server only requests data.



This may seem like a clean and pleasant section of concerns. While this can lead to a nice, clean separation of concerns, inevitably some parts of the application logic or view logic are duplicated on both the server and the client (usually in different languages).

Also, a client-only application cannot serve HTML to users or crawlers. This slows down the performance of the initial page load and also makes it difficult for SEO to work.


Sources:

+3


source







All Articles