Best way to handle a user generated page
A bit of an interesting one here. I'm currently in the process of building a POC for a page builder for a page in my application. The idea is to have the user compose this page (in some sort of back office) from a set of predefined blocks that they can add, remove, reorder and do some basic configuration. Some of these blocks will have to fetch data over an API when they're loaded in the actual page.
I'm wondering if there's some optimisation I can do to cache the result of this page's construction so I don't have to go through the process of reconstructing it the page every time someone loads it?
I figure I might need to have some sort of job run that compiles it down to a static page and then serve that static page from my route?
Open to suggestions and general musings on this.
I'm wondering if there's some optimisation I can do to cache the result of this page's construction so I don't have to go through the process of reconstructing it the page every time someone loads it?
I figure I might need to have some sort of job run that compiles it down to a static page and then serve that static page from my route?
Open to suggestions and general musings on this.
