I'm working on an angular project with more than 60 000 pages, the goal would be to have prerendering for all of them cause we want customer to have easy access to those pages even with poor internet connection. First I would like to know if angular universal is able to deal with that much pages during build time given the right infrastructure ? Then if it's possible to cache prerender pages so that during following build we won't have to generate those static pages again if they have not been updated since. Also we have a host application with multiple angular micro front end on different repositories. Is it possible to have the host node server managing all ssr request from all apps, or do I need one server for each app on each repository (the issue being that we need the url indexed by the bot to be the domain of the host not the one from the remote apps). For exemple if host is hostapp.com, and my remote is remoteArticles.com (the remote being a section of host with all my articles pages), I want my urls articles pages when indexed to be hostapp.com/remoteArticles/article-1 and not remoteArticles.com/article-1. I know that I can use canonical urls but I'm not sure it's enough to only have remote app pages rendered through the host app. I'm not sure if I was clear, let me know if I'm not. Thanks I already have angular universal set up on working for host pages, I now need to prerender thousand of pages from remote apps, and I'm not sure how to be the most efficiant, maybe not doing prerendering and only server side rendering. I thought of using scully but I'm not sure they are up to date with angular 18, I'm now using native federation to communicate between host and remote Continue reading...
