Syncing objects to a remote server, and caching on local storage

What’s the best method of sycing objects (as JSON) to a remote server, with local caching?

Is the UX affected negatively by fully cacheable pages?

I want to have fully cacheable pages in my websites, but one cannot do that if they contain user-specific data, like the userbar or things in the UI that can change depending on the permissions the user has.

What reasons are there to reduce the max-age of a logo to just 8 days?

Most websites set max-age=31536000 (1 year) on the Cache-control headers of static assets such as logo images. Examples:

I am trying to figure out the best way to understand how to cache domain objects

I’ve always done this wrong, I’m sure a lot of others have too, hold a reference via a map and write through to DB etc..

Caching by in-memory dictionaries. Are we doing it all wrong?

This approach is pretty much the accepted way to do anything in our company.

Is it ok to ignore poor performance for a resource that will be cached?

Let’s say I have a web service that is poorly written and inefficient, but it’s output is cached so there’s no bottleneck. Do you just leave it? Would you go as far as to take deliberate shortcuts knowing that performance problems will be masked?

Idea to develop a caching server between IIS and SQL Server

I work on a few high traffic websites that all share the same database and that are all heavily database driven. Our SQL server is max-ed out and, although we have already implemented many changes that have helped but the server is still working too hard.

Versioned Resources to Improve Cacheability

Here’s an API concept which could be useful for performance optimisation. It’s an example of key-based cache expiry applied to a broader internet-wide context instead of the internal Memcached-style scenario it seems to be mostly used for.

Shared Cache – Invalidation Best Practice

I’d like to know what would be a better approach to invalidate/update cache objects.

Are “conditional” caching policies ever actually useful?

I’m designing an abstraction over ASP.Net’s built in caching to make it not so horrible to use. One design decision I’m having to look at is if I should restrict people to using just one cache policy on each item.