Hi Donald, Yes, I do think that's better. This are some of the reason's in no particular order:
- spread the traffic over different origins. this leads to faster boot-time - less traffic to my own server, so it can serve more users, or faster (oh and cheaper too ;) ) - depending on CDN, resources are closer to the user, again faster loading - much greater change of a cache-hit by the user. Again faster loading - maintained by a company that has made a business out of this. So keeping it up is of vital importance to them. (some free cdn's excluded here) This is the only downside: - Out of my control. Might go down while I'm not looking About that last point, see the last one of the pluses. If the stuff that's hosted on there is really needed for my critical path, I can host a backup-set of resources on my own server. Heck I can even keep a list of different CDN's that have that resource and cycle trough that. If none of them are up, I can always server the resource from my server. Of course my own servers/applications never-ever-never go down ;) In case of failure do not forget to inform your user. Tell them there is network congestion, and it will take a bit longer. If all fails, don't leave them hanging. Oh, it just hit me. If you are using free CDN's (also those are not all alike, the free Google CDN is probably a lot more reliable then some unnamed never-heard of one) there might be some slowdowns, or even unavailability. This can usually be cured by selecting a better one, and having the backup-strategy in place. Or just use a paid one. Changes are, your app will seldom go over the free tier those provide;) Regards Sander -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
