Not sure i get the idea, but i suppose it's about adding the hit counts in the response and then query the URL from the backend ? If yes, that's an interesting

Not sure i get the idea, but i suppose it's about adding the hit counts in the response and then query the URL from the backend ? If yes, that's an interesting approach, but in my opinion it has two drawbacks. - It requires a loop through each entities that is supposed to have it's hits counted periodically and query Varnish for it. - There can be hits not counted if for some reason we purge Varnish (not sure about this assertion tho) between two polls. http://cyqui.fr/blog/Varnish-counting-hits-on-cached-objects.html#using-objects-cache-hits http://cyqui.fr/blog/Varnish-counting-hits-on-cached-objects... While with Redis as the counter storage: - We can fetch periodically keys matching 'view_counter_${entity_type}_${entity_id}' (using KEYS command) and it gives a lot of flexibility application side - We do not have to worry about the counters states