My opinion is that server side rendering is just temporary thing for search engine optimizations.
But, if you really need it, you could use Node.js as client to your go api. Then, nginx as a front proxy, could serve static assets with and without backend data from go api. For example, if Node.js is running, then proxy index.html request there. If not just reply with empty html that will be filled by requests from browser to your go api. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
