4 ms·
I understand the architecture you are describing, and I don't think that it is trivial. My confusion is over what really constitutes a "fully static" app.
by pyrophane 10y ago
I understand the architecture you are describing, and I don't think that it is trivial. My confusion is over what really constitutes a "fully static" app.
- jqueryin 10y agoIMO, static doesn't have to have a correlation to being simpler. HTML, CSS, JS, and media are all static assets but you're welcome to request whatever datatypes you want behind the scenes via AJAX and/or CORs. The benefits are entirely in the rendering speeds of an optimized web server and cache layer. Also, this approach plays extremely nicely with CDNs. Difficulties can arise if you have to begin dealing with versioning of your assets to avoid cache invalidation, but that's what a proper build process can add to the static site.
- aeosynth 10y agoIs the performance/simplicity that much better than setting up Cloudflare yourself?
- igorgue 10y agoIn this particular case, my understanding is, the fully static code is just the frontend, in other words to not render HTML from your Web Server to the Browsers.