Work breakdown for FxA-49: CDN about fxa HOT 8 CLOSED

If we're looking into this, should we also look into cache-friendly URLs for static assets?

If we add a hash of the contents to the file name, matching URLs can be served with a Cache-Control: max-age=31536000 header and repeat visits to the content server would not need to download those resources at all. This may have a bigger overall effect than a CDN would (which is not to say I don't think we should move to a CDN too; we should).

from fxa.

If we're looking into this, should we also look into cache-friendly URLs for static assets?

Static resource URLs should be cache friendly already, and served with long lived cache headers:

This may have a bigger overall effect than a CDN would (which is not to say I don't think we should move to a CDN too; we should).

The caching is in place to help repeat visits, now we want to speed up the load time of first time visitors.

from fxa.

Whoops, I'm sorry.

from fxa.

@rfk - is the "work breakdown" portion of this already in progress?

from fxa.

from mtg: @jrgm mentions that we'll have to use a subdomain to serve static resources and we should think about how we can continue to use the same RPM for both stage and prod, w/o performing a rewrite on all of the static HTML files.

from fxa.

is the "work breakdown" portion of this already in progress?

nope, those high-level notes are as far as I got with it - this needs an owner to take on the task of actually figuring out and writing up all the details.

from fxa.

In the interests of clarity: the desired outcome for this issue is a feature card in https://github.com/mozilla/fxa/tree/master/features describing what we'll need to put in place to use a CDN, and how we'll measure its success.

@shane-tomlinson we took the liberty of assigning this to you during sprint planning meeting; don't hesitate to de-assign yourself if that doesn't seem appropriate :-)

from fxa.

ref mozilla/fxa-content-server#3101, mozilla/fxa-content-server#3447, mozilla/fxa-content-server#3448, mozilla/fxa-content-server#3449

from fxa.