Popular posts

I do it like @adambene. Putting the code into microservices.

That is, because of the corporate environment, I have to stay backend-agnostic. Google and other web crawlers can't parse our SPA's. Therefore, we don't need to care for SEO or having content inside of <noscript>. The first-page-hit looks a bit slow. But since we have our company CDN established, even that seems acceptable regarding speed. Additionally, we store web assets in HTML app cache. On corporate side we have 3000 office PC's across the globe, due to some routing issues, people can't judge if our side is slow due to Coding/Libraries/Frameworks or due to network issues.

On React.js Node.js apps, I am also not reusing much of the code. We cache web assets via service workers -> ponyfoo.com/articles/progressive-networking-servi… But we use a little different approach.

1. On page load -> opac overlay with loading spinner rendered from static index.html
2. Document ready -> Initialize the SPA
3. Check if something according to URL is in service worker cache
   • If not -> React render() HTML, store render() result in service worker
   • If yes -> React fetch cached HTML and render it, React render() semi opac overlay with loading spinner, fetch current data
   • On data received -> destroy overlay, React render() HTML, store render() result in service worker

It's still not SEO friendly and it's also not progressive-enhancement, but getting stuff done.