There is still a few things to know for developers wanting to use SSR:
- Why doing SSR? SEO has always been the main reason but the faster first paint is often the real benefit.
- It creates a new browser workflow. First render, then interactivity, then programmatic navigation. It can creates surprising behaviors.
- Executing your code base on a double environment (Browser & Node) has a few tricks (mention of RazzleJS).
- Defining when your page is fully loaded for the server rendering
- How to restart client side on a page already rendered. Most frameworks use hydration but Angular uses a second rendering.
- SSR can be on demand or on build, it could save a lot of server processing.
- Frameworks exists to ease all these points, you will probably want consider Next and Nuxt.