Caching is an evil
I know ‘Caching’ was created to ease out the network resources but i have seen the situations where it emerged as the biggest evil.
I can remember many situations when the website is updated but still, live website was showing old content plus the developer forgot that caching is ON. Just imagine, development team is doing a night out to resolve this issue and after spending countless hours, people came to know that page is cached. Believe me, i have seen many situations like these. 😛
Next , when Client asks why it happened? They receive a very familiar reply “Caching Issue”. I got caught in this situation few times and my reply was the same as above. Client nodded and everyone forgot.
Lately, client put a query that what is this caching? why it is a recurring issue? why can’t we disable it ? its more of a pain for us. Prior to this, client nodded whenever this issue came unaware of the issue so I must admit that this is a query asked for some personal knowledge.
Let’s see how can we relate it to common terms.
A person goes to a restaurant and orders something from la-carte and then waits for the order to arrive. Few minutes and food is on the table.yummy!!! Did anybody notice that there is some pickle,some salad, some sausages are already on the table? Nobody ordered them but they are already there on the table.Though they doesn’t form the complete meal but still without them food doesn’t taste well.
So this already prepared item on the table can be imagined as cached items. As a user,nobody notices this item but it forms a necessary requirement for a smooth web experience. Similar to these items, few/all sections of the site are prepared once and can be served again and again. if caching is removed, then each section/item has to be freshly prepared and served which will take additional time and consume more web resources.
I hope this example make some sense and only your opinion can prove that. Please ask any question or provide more creative idea to explain caching.