Explain better in the DOCS advantages of cache (CDN)

[juanmaguitar]

https://403page.com/scaling-for-volume-with-frontity-cloudflare/

with that setup, he is pretty much testing how well cloudflare CDN works because 99.89% of the requests when to the CF CDN and that obviously scales to the infinitum but that’s one of the points I always try to make: Frontity is as fast and as scalable as a static site as soon as you add a CDN and you should add a CDN (by the way, all the modern static site hostings like Now, Netlify, Surge… have CDNs) For the rest of 0.11% of the requests that went into Frontity: If you use a Node server: much more scalable than WordPress, because it’s Node (which by default is more scalable for its I/O) and it’s stateless so you can easily scale horizontally. If you use Serverless: then this part is also infinite scalable, like a CDN. and finally the last thing that needs to be taken into consideration to scale Frontity is how well you cache the REST API

[juanmaguitar]

I think creating a "cache" subcategory under "Architecture" can be a good place to document this. We should document either cache at a Frontend level and cache at a WP level

Related thread: https://community.frontity.org/t/optimize-wordpress-for-rest-api/2523