Wouldn't front end caching need to be a bit generalized? Meaning that if I have some web page generated with my username "amolakn", the page with "amolakn" shouldn't be cached right? It should be the generic page with the content, but generalized so that it can be called when any username needs it.
kamikaze
A Front-End Cache sounds quite similar to the cache we implemented for our Proxy in 213. The load balancer seems to be a form of a proxy as it is in fact acting as a 'middle man' and distributing requests accordingly.
ferozenaina
@amolakn: I think only common data such as fonts, stylesheets, icons, boilerplate text get cached. The cache itself would determine which items are general and store them.
From researching from different sources, I got this:
Caching maximizes the output of a web server. Key - the apache/nginx server backend shouldn’t have to regenerate the same dynamic content scratch every time it’s accessed. Varnish accelerates responses to HTTP requests and reduce server workload by handling requests BEFORE they make it to the server. If it doesn’t have a request cached, it will forward the request to your backend and then cache its output.
These caches can be stored on disk or memory (much faster).
Wouldn't front end caching need to be a bit generalized? Meaning that if I have some web page generated with my username "amolakn", the page with "amolakn" shouldn't be cached right? It should be the generic page with the content, but generalized so that it can be called when any username needs it.
A Front-End Cache sounds quite similar to the cache we implemented for our Proxy in 213. The load balancer seems to be a form of a proxy as it is in fact acting as a 'middle man' and distributing requests accordingly.
@amolakn: I think only common data such as fonts, stylesheets, icons, boilerplate text get cached. The cache itself would determine which items are general and store them.
From researching from different sources, I got this: Caching maximizes the output of a web server. Key - the apache/nginx server backend shouldn’t have to regenerate the same dynamic content scratch every time it’s accessed. Varnish accelerates responses to HTTP requests and reduce server workload by handling requests BEFORE they make it to the server. If it doesn’t have a request cached, it will forward the request to your backend and then cache its output.
These caches can be stored on disk or memory (much faster).