Progressive Web Application Development by Example

Cache falling back to network

The most common pattern I see employed in service workers is the cache falling back to the network. It's very popular because checking for an asset's presence in your cache means that it can return immediately. If it does not, you still have the network fallback retrieving it as fast as possible.

Any asset that is not precached or previously cached from the same pattern would be accessible, assuming you are online. The following image shows the interactions involved:

I say that this is probably the most common pattern used because any asset that is not precached could comfortably fit into this pattern. The podcast ...