$30 off During Our Annual Pro Sale. View Details »

CloudFront BEST PRACTICES & ANTI-PATTERNS

CloudFront BEST PRACTICES & ANTI-PATTERNS

CloudFront is a Content Delivery Network (CDN) provided by Amazon Web Services (AWS). It integrates seamlessly with other AWS services.

Agenda of this presentation is
1. CloudFront OVERVIEW
2. CloudFront BEST PRACTICES & ANTI-PATTERNS

This presentation was prepared for AWS Sydney Meetup.

Abhishek Tiwari

August 07, 2013
Tweet

More Decks by Abhishek Tiwari

Other Decks in Technology

Transcript

  1. About me Solutions Architect Early AWS adopter (2007) Built Cotton

    On Group’s AWS Infrastructure (2012) Wednesday, 7 August 13
  2. CloudFront (CF) Content Delivery Network Serves Static and Dynamic Content

    Global, Redundant, Scalable Wednesday, 7 August 13
  3. CloudFront (CF) Content Delivery Network Serves Static and Dynamic Content

    Global, Redundant, Scalable Low Latency, High Bandwidth Wednesday, 7 August 13
  4. CloudFront (CF) Content Delivery Network Serves Static and Dynamic Content

    Global, Redundant, Scalable Low Latency, High Bandwidth Cost Effective: Transparent, PAYG, Price Classes Wednesday, 7 August 13
  5. CloudFront (CF) Content Delivery Network Serves Static and Dynamic Content

    Global, Redundant, Scalable Low Latency, High Bandwidth Cost Effective: Transparent, PAYG, Price Classes NO Edge Side Includes (ESI) Wednesday, 7 August 13
  6. CF Concepts Distribution Delivery Method (Download or Streaming) CNAME Aliases

    (1-10) Origin Server/s (M:M) Wednesday, 7 August 13
  7. CF Concepts Distribution Delivery Method (Download or Streaming) CNAME Aliases

    (1-10) Origin Server/s (M:M) Domain Name, Origin ID, Origin Protocol Wednesday, 7 August 13
  8. CF Concepts Distribution Delivery Method (Download or Streaming) CNAME Aliases

    (1-10) Origin Server/s (M:M) Domain Name, Origin ID, Origin Protocol Object/s (Object Path/Cache Key) Wednesday, 7 August 13
  9. CF Concepts Distribution Delivery Method (Download or Streaming) CNAME Aliases

    (1-10) Origin Server/s (M:M) Domain Name, Origin ID, Origin Protocol Object/s (Object Path/Cache Key) Cache Behavior/s (1-10, 1:1, Ordered) Wednesday, 7 August 13
  10. CF Concepts Distribution Delivery Method (Download or Streaming) CNAME Aliases

    (1-10) Origin Server/s (M:M) Domain Name, Origin ID, Origin Protocol Object/s (Object Path/Cache Key) Cache Behavior/s (1-10, 1:1, Ordered) Path Patterns, Origin ID, Viewer Protocol, Minimum TTL, Cookies/ Query String Forwarding Wednesday, 7 August 13
  11. CF Concepts Distribution Delivery Method (Download or Streaming) CNAME Aliases

    (1-10) Origin Server/s (M:M) Domain Name, Origin ID, Origin Protocol Object/s (Object Path/Cache Key) Cache Behavior/s (1-10, 1:1, Ordered) Path Patterns, Origin ID, Viewer Protocol, Minimum TTL, Cookies/ Query String Forwarding Edge Location (42+) Wednesday, 7 August 13
  12. CF Concepts Distribution Delivery Method (Download or Streaming) CNAME Aliases

    (1-10) Origin Server/s (M:M) Domain Name, Origin ID, Origin Protocol Object/s (Object Path/Cache Key) Cache Behavior/s (1-10, 1:1, Ordered) Path Patterns, Origin ID, Viewer Protocol, Minimum TTL, Cookies/ Query String Forwarding Edge Location (42+) Viewer (GET, Range GET, HEAD Requests) Wednesday, 7 August 13
  13. CF Concepts http:/ /mycontent.cloudfront.net/photos/profile.png Cache Key: photos/profile.png (Same for HTTP/HTTPS)

    Cache Key: object path relative to origin + forwarded query string/cookies Wednesday, 7 August 13
  14. CF Concepts Dynamic Content http:/ /mycontent.cloudfront.net/photos/profile.png Cache Key: photos/profile.png (Same

    for HTTP/HTTPS) Cache Key: object path relative to origin + forwarded query string/cookies Wednesday, 7 August 13
  15. CF Concepts Dynamic Content Static Content http:/ /mycontent.cloudfront.net/photos/profile.png Cache Key:

    photos/profile.png (Same for HTTP/HTTPS) Cache Key: object path relative to origin + forwarded query string/cookies Wednesday, 7 August 13
  16. How it works 1. Client request file 2. If file

    in cache CF return file Nearest Edge Location a. If file not in cache, CF request to origin b. Origin returns file, status 200, cached in CF 1. Client request file 2. If file in cache CF return file Nearest Edge Location a. If file in cache but expired, CF request to origin b. Origin returns 304, CF keeps file in cache Routing based on low latency/price class Routing based on low latency/price class Condition GET Wednesday, 7 August 13
  17. Distribution Download Distribution Viewer Protocol HTTP/HTTPS Origin: S3 or Custom

    Cookies/Query String Forwarding Wednesday, 7 August 13
  18. Distribution Download Distribution Viewer Protocol HTTP/HTTPS Origin: S3 or Custom

    Cookies/Query String Forwarding Streaming Distribution Wednesday, 7 August 13
  19. Distribution Download Distribution Viewer Protocol HTTP/HTTPS Origin: S3 or Custom

    Cookies/Query String Forwarding Streaming Distribution Viewer Protocol: Adobe RTMP Wednesday, 7 August 13
  20. Distribution Download Distribution Viewer Protocol HTTP/HTTPS Origin: S3 or Custom

    Cookies/Query String Forwarding Streaming Distribution Viewer Protocol: Adobe RTMP Origin: S3 only (No Custom) Wednesday, 7 August 13
  21. Distribution Download Distribution Viewer Protocol HTTP/HTTPS Origin: S3 or Custom

    Cookies/Query String Forwarding Streaming Distribution Viewer Protocol: Adobe RTMP Origin: S3 only (No Custom) Dynamic/Adoptive Streaming (Adjust bit rate during playback) Wednesday, 7 August 13
  22. Query String Forwarding Forward query string to origin Multiple parameters,

    order/case sensitive Order sensitive: Two objects in CF Wednesday, 7 August 13
  23. Query String Forwarding Forward query string to origin Multiple parameters,

    order/case sensitive Order sensitive: Two objects in CF http:/ /d111111abcdef8.cloudfront.net/images/image.jpg?height=a&width=b Wednesday, 7 August 13
  24. Query String Forwarding Forward query string to origin Multiple parameters,

    order/case sensitive Order sensitive: Two objects in CF http:/ /d111111abcdef8.cloudfront.net/images/image.jpg?height=a&width=b http:/ /d111111abcdef8.cloudfront.net/images/image.jpg?width=b&height=a Wednesday, 7 August 13
  25. Query String Forwarding Forward query string to origin Multiple parameters,

    order/case sensitive Order sensitive: Two objects in CF http:/ /d111111abcdef8.cloudfront.net/images/image.jpg?height=a&width=b http:/ /d111111abcdef8.cloudfront.net/images/image.jpg?width=b&height=a Case sensitive: Two objects in CF Wednesday, 7 August 13
  26. Query String Forwarding Forward query string to origin Multiple parameters,

    order/case sensitive Order sensitive: Two objects in CF http:/ /d111111abcdef8.cloudfront.net/images/image.jpg?height=a&width=b http:/ /d111111abcdef8.cloudfront.net/images/image.jpg?width=b&height=a Case sensitive: Two objects in CF http:/ /d111111abcdef8.cloudfront.net/images/image.jpg?type=png Wednesday, 7 August 13
  27. Query String Forwarding Forward query string to origin Multiple parameters,

    order/case sensitive Order sensitive: Two objects in CF http:/ /d111111abcdef8.cloudfront.net/images/image.jpg?height=a&width=b http:/ /d111111abcdef8.cloudfront.net/images/image.jpg?width=b&height=a Case sensitive: Two objects in CF http:/ /d111111abcdef8.cloudfront.net/images/image.jpg?type=png http:/ /d111111abcdef8.cloudfront.net/images/image.jpg?type=PNG Wednesday, 7 August 13
  28. Cookies Forwarding Forwarded cookies (FC): NV pairs, not attributes If

    choose to forward cookies to origin, Wednesday, 7 August 13
  29. Cookies Forwarding Forwarded cookies (FC): NV pairs, not attributes If

    choose to forward cookies to origin, Can forward all cookies, OR Wednesday, 7 August 13
  30. Cookies Forwarding Forwarded cookies (FC): NV pairs, not attributes If

    choose to forward cookies to origin, Can forward all cookies, OR Only specified cookies Wednesday, 7 August 13
  31. Cookies Forwarding Forwarded cookies (FC): NV pairs, not attributes If

    choose to forward cookies to origin, Can forward all cookies, OR Only specified cookies Object path+FC uniquely identify in CF Wednesday, 7 August 13
  32. Cookies Forwarding Forwarded cookies (FC): NV pairs, not attributes If

    choose to forward cookies to origin, Can forward all cookies, OR Only specified cookies Object path+FC uniquely identify in CF NV pair/Case sensitive Wednesday, 7 August 13
  33. Origin S3 Origin: Best for Static media content (Image, Video,

    Audio) Custom Origin: Best for Static application content (JS, CSS, Fonts) Wednesday, 7 August 13
  34. Origin S3 Origin: Best for Static media content (Image, Video,

    Audio) Custom Origin: Best for Static application content (JS, CSS, Fonts) Custom Origin: Best for Dynamic media content (HTML, Thumbnails) Wednesday, 7 August 13
  35. Make a note Eventual Consistency 10 Origin Servers per CF

    Distribution Wednesday, 7 August 13
  36. Make a note Eventual Consistency 10 Origin Servers per CF

    Distribution 10 Cache Behavior per CF Distribution Wednesday, 7 August 13
  37. Make a note Eventual Consistency 10 Origin Servers per CF

    Distribution 10 Cache Behavior per CF Distribution 10 CNAME per CF Distribution Wednesday, 7 August 13
  38. Make a note Eventual Consistency 10 Origin Servers per CF

    Distribution 10 Cache Behavior per CF Distribution 10 CNAME per CF Distribution 10 Cookies forwarded per Cache Behavior Wednesday, 7 August 13
  39. Cache Invalidation Programmatic Cache Invalidation Cache Invalidation is expensive Unmanageable

    if you have object dependencies 3 invalidation requests at any given time Wednesday, 7 August 13
  40. Cache Invalidation Programmatic Cache Invalidation Cache Invalidation is expensive Unmanageable

    if you have object dependencies 3 invalidation requests at any given time Each invalidation request can included maximum of 1000 files Wednesday, 7 August 13
  41. Cache Invalidation Invalidation takes time to propagate across all edge

    locations (5-15 minutes) Wednesday, 7 August 13
  42. Cache Invalidation Invalidation takes time to propagate across all edge

    locations (5-15 minutes) Deal breaker: browser cache Wednesday, 7 August 13
  43. Cache Invalidation Invalidation takes time to propagate across all edge

    locations (5-15 minutes) Deal breaker: browser cache Versioning is best way to avoid the invalidation related issues Wednesday, 7 August 13
  44. Versioning CF relies on Origin Servers for versioning S3 supports

    versioning Version enabled Custom Origin Wednesday, 7 August 13
  45. Versioning Versioning using query strings File name plus query string

    with version /static/profile.png?versionID=123 Wednesday, 7 August 13
  46. Versioning Versioning using query strings File name plus query string

    with version /static/profile.png?versionID=123 Versioning using content based hash key Wednesday, 7 August 13
  47. Versioning Versioning using query strings File name plus query string

    with version /static/profile.png?versionID=123 Versioning using content based hash key File name as unique key based on file content /static/712vds57tr18929812312enb.png Wednesday, 7 August 13
  48. Versioning Versioning using query strings File name plus query string

    with version /static/profile.png?versionID=123 Versioning using content based hash key File name as unique key based on file content /static/712vds57tr18929812312enb.png Versioning using prefix/suffix Wednesday, 7 August 13
  49. Versioning Versioning using query strings File name plus query string

    with version /static/profile.png?versionID=123 Versioning using content based hash key File name as unique key based on file content /static/712vds57tr18929812312enb.png Versioning using prefix/suffix File name with version prefix/suffix /static/profile_123.png Wednesday, 7 August 13
  50. Versioning Versioning using query strings File name plus query string

    with version /static/profile.png?versionID=123 Versioning using content based hash key File name as unique key based on file content /static/712vds57tr18929812312enb.png Versioning using prefix/suffix File name with version prefix/suffix /static/profile_123.png File name with version prefix/suffix /static/profile_ 712vds57tr18929812312enb.png Wednesday, 7 August 13
  51. Versioning Versioning using query strings File name plus query string

    with version /static/profile.png?versionID=123 Versioning using content based hash key File name as unique key based on file content /static/712vds57tr18929812312enb.png Versioning using prefix/suffix File name with version prefix/suffix /static/profile_123.png File name with version prefix/suffix /static/profile_ 712vds57tr18929812312enb.png You can use a mixed versioning approach Wednesday, 7 August 13
  52. Versioning using query strings CF supports versioning using query strings

    forwarding Versioning enabled Origin (Custom/S3) Wednesday, 7 August 13
  53. Versioning using query strings CF supports versioning using query strings

    forwarding Versioning enabled Origin (Custom/S3) For S3 Content Wednesday, 7 August 13
  54. Versioning using query strings CF supports versioning using query strings

    forwarding Versioning enabled Origin (Custom/S3) For S3 Content On object upload version enabled S3 bucket will return x-amz-version-id Wednesday, 7 August 13
  55. Versioning using query strings CF supports versioning using query strings

    forwarding Versioning enabled Origin (Custom/S3) For S3 Content On object upload version enabled S3 bucket will return x-amz-version-id profile.png Wednesday, 7 August 13
  56. Versioning using query strings CF supports versioning using query strings

    forwarding Versioning enabled Origin (Custom/S3) For S3 Content On object upload version enabled S3 bucket will return x-amz-version-id profile.png Upload to S3 Wednesday, 7 August 13
  57. Versioning using query strings CF supports versioning using query strings

    forwarding Versioning enabled Origin (Custom/S3) For S3 Content On object upload version enabled S3 bucket will return x-amz-version-id profile.png Upload to S3 static/images/profile.png Wednesday, 7 August 13
  58. Versioning using query strings CF supports versioning using query strings

    forwarding Versioning enabled Origin (Custom/S3) For S3 Content On object upload version enabled S3 bucket will return x-amz-version-id profile.png Upload to S3 static/images/profile.png Return x-amz-version-id Wednesday, 7 August 13
  59. Versioning using query strings CF supports versioning using query strings

    forwarding Versioning enabled Origin (Custom/S3) For S3 Content On object upload version enabled S3 bucket will return x-amz-version-id profile.png Upload to S3 static/images/profile.png Return x-amz-version-id static/images/profile.png? versionId=644c69e148 Wednesday, 7 August 13
  60. Versioning using query strings Versionify Application content Use Build Number

    or Hash of GIT/HG Head photo.css, app.css, profile.css photo.js, app.js, profile.js Wednesday, 7 August 13
  61. Versioning using query strings Versionify Application content Use Build Number

    or Hash of GIT/HG Head photo.css, app.css, profile.css photo.js, app.js, profile.js Minify+Combine Wednesday, 7 August 13
  62. Versioning using query strings Versionify Application content Use Build Number

    or Hash of GIT/HG Head photo.css, app.css, profile.css photo.js, app.js, profile.js Minify+Combine main.css main.js Wednesday, 7 August 13
  63. Versioning using query strings Versionify Application content Use Build Number

    or Hash of GIT/HG Head photo.css, app.css, profile.css photo.js, app.js, profile.js Minify+Combine main.css main.js Versionify Wednesday, 7 August 13
  64. Versioning using query strings Versionify Application content Use Build Number

    or Hash of GIT/HG Head photo.css, app.css, profile.css photo.js, app.js, profile.js Minify+Combine main.css main.js Versionify main.css?v=468df6b main.js?v=468df6b Wednesday, 7 August 13
  65. Versioning using content based hash key File name is an

    unique hash key generated from file content (MD5) Wednesday, 7 August 13
  66. Versioning using content based hash key File name is an

    unique hash key generated from file content (MD5) For S3 content Wednesday, 7 August 13
  67. Versioning using content based hash key File name is an

    unique hash key generated from file content (MD5) For S3 content Before uploading to S3 generate MD5 hash for file Wednesday, 7 August 13
  68. Versioning using content based hash key File name is an

    unique hash key generated from file content (MD5) For S3 content Before uploading to S3 generate MD5 hash for file Use hash as file name to upload on S3 Wednesday, 7 August 13
  69. Versioning using content based hash key File name is an

    unique hash key generated from file content (MD5) For S3 content Before uploading to S3 generate MD5 hash for file Use hash as file name to upload on S3 Avoid content duplication by comparing MD5 hashes Wednesday, 7 August 13
  70. Versioning using content based hash key File name is an

    unique hash key generated from file content (MD5) For S3 content Before uploading to S3 generate MD5 hash for file Use hash as file name to upload on S3 Avoid content duplication by comparing MD5 hashes profile.jpg Wednesday, 7 August 13
  71. Versioning using content based hash key File name is an

    unique hash key generated from file content (MD5) For S3 content Before uploading to S3 generate MD5 hash for file Use hash as file name to upload on S3 Avoid content duplication by comparing MD5 hashes profile.jpg MD5 Hash File Name Wednesday, 7 August 13
  72. Versioning using content based hash key File name is an

    unique hash key generated from file content (MD5) For S3 content Before uploading to S3 generate MD5 hash for file Use hash as file name to upload on S3 Avoid content duplication by comparing MD5 hashes profile.jpg MD5 Hash File Name b723eh0f0df.png Wednesday, 7 August 13
  73. Versioning using content based hash key File name is an

    unique hash key generated from file content (MD5) For S3 content Before uploading to S3 generate MD5 hash for file Use hash as file name to upload on S3 Avoid content duplication by comparing MD5 hashes profile.jpg MD5 Hash File Name b723eh0f0df.png Upload to S3 Wednesday, 7 August 13
  74. Versioning using content based hash key File name is an

    unique hash key generated from file content (MD5) For S3 content Before uploading to S3 generate MD5 hash for file Use hash as file name to upload on S3 Avoid content duplication by comparing MD5 hashes profile.jpg MD5 Hash File Name b723eh0f0df.png Upload to S3 static/images/b723eh0f0df.png Wednesday, 7 August 13
  75. Versioning using content based hash key For application content use

    a pipeline file names generated using MD5 hash of file content Wednesday, 7 August 13
  76. Versioning using content based hash key For application content use

    a pipeline file names generated using MD5 hash of file content photo.css, app.css, profile.css photo.js, app.js, profile.js Wednesday, 7 August 13
  77. Versioning using content based hash key For application content use

    a pipeline file names generated using MD5 hash of file content photo.css, app.css, profile.css photo.js, app.js, profile.js Minify+Combine Wednesday, 7 August 13
  78. Versioning using content based hash key For application content use

    a pipeline file names generated using MD5 hash of file content photo.css, app.css, profile.css photo.js, app.js, profile.js Minify+Combine main.css main.js Wednesday, 7 August 13
  79. Versioning using content based hash key For application content use

    a pipeline file names generated using MD5 hash of file content photo.css, app.css, profile.css photo.js, app.js, profile.js Minify+Combine main.css main.js MD5 Hash File Name Wednesday, 7 August 13
  80. Versioning using content based hash key For application content use

    a pipeline file names generated using MD5 hash of file content photo.css, app.css, profile.css photo.js, app.js, profile.js Minify+Combine main.css main.js MD5 Hash File Name 8972bw7dyf2h.css 67bfwu9hhuw.js Wednesday, 7 August 13
  81. Compression Compressed content is served faster and uses less bandwidth

    CF can serve both compressed and uncompressed version of files Wednesday, 7 August 13
  82. Compression Compressed content is served faster and uses less bandwidth

    CF can serve both compressed and uncompressed version of files Depends on viewer or browser request Wednesday, 7 August 13
  83. Compression Compressed content is served faster and uses less bandwidth

    CF can serve both compressed and uncompressed version of files Depends on viewer or browser request To receive compressed content browser must include Accept-Encoding: gzip in the request header Wednesday, 7 August 13
  84. Compression Compressed content is served faster and uses less bandwidth

    CF can serve both compressed and uncompressed version of files Depends on viewer or browser request To receive compressed content browser must include Accept-Encoding: gzip in the request header For compression CF relies on the custom origin servers Wednesday, 7 August 13
  85. Compression Compressed content is served faster and uses less bandwidth

    CF can serve both compressed and uncompressed version of files Depends on viewer or browser request To receive compressed content browser must include Accept-Encoding: gzip in the request header For compression CF relies on the custom origin servers S3 does not perform the compression Wednesday, 7 August 13
  86. Compression S3 can store both gzip and non-gzip versions of

    the file in the same bucket Wednesday, 7 August 13
  87. Compression S3 can store both gzip and non-gzip versions of

    the file in the same bucket When uploading gzip file to Amazon S3 set Content-Encoding to gzip Wednesday, 7 August 13
  88. Compression S3 can store both gzip and non-gzip versions of

    the file in the same bucket When uploading gzip file to Amazon S3 set Content-Encoding to gzip On-the-fly compression by custom origin server (Nginx, Apache) Wednesday, 7 August 13
  89. Compression S3 can store both gzip and non-gzip versions of

    the file in the same bucket When uploading gzip file to Amazon S3 set Content-Encoding to gzip On-the-fly compression by custom origin server (Nginx, Apache) Compress: HTML, CSS, JS etc Wednesday, 7 August 13
  90. Compression S3 can store both gzip and non-gzip versions of

    the file in the same bucket When uploading gzip file to Amazon S3 set Content-Encoding to gzip On-the-fly compression by custom origin server (Nginx, Apache) Compress: HTML, CSS, JS etc Compress Image: JPEG, WebP (Q= 0-100) Wednesday, 7 August 13
  91. Expiration Use one/both of these On Origin server set Cache-Control

    max-age header In Cache Behavior set Minimum TTL Wednesday, 7 August 13
  92. Expiration Use one/both of these On Origin server set Cache-Control

    max-age header In Cache Behavior set Minimum TTL Date header/Age header (RFC 2616) Wednesday, 7 August 13
  93. Expiration Use one/both of these On Origin server set Cache-Control

    max-age header In Cache Behavior set Minimum TTL Date header/Age header (RFC 2616) Avoid Expire header Wednesday, 7 August 13
  94. Expiration Browser cachability issues (known bug) Set Cache-Control max-age or

    Minimum TTL very far future Wednesday, 7 August 13
  95. Expiration Browser cachability issues (known bug) Set Cache-Control max-age or

    Minimum TTL very far future Depending on request frequency, CloudFront might remove the object before its expiration Wednesday, 7 August 13
  96. Expiration Browser cachability issues (known bug) Set Cache-Control max-age or

    Minimum TTL very far future Depending on request frequency, CloudFront might remove the object before its expiration Default expiration 24hrs Wednesday, 7 August 13
  97. Expiration Browser cachability issues (known bug) Set Cache-Control max-age or

    Minimum TTL very far future Depending on request frequency, CloudFront might remove the object before its expiration Default expiration 24hrs Objects are cached for max {Cache-Control max-age directive, Cache Behavior Minimum TTL} Wednesday, 7 August 13
  98. Domain Sharding To increase client side performance On average 100+

    resources on an ecommerce page Wednesday, 7 August 13
  99. Domain Sharding To increase client side performance On average 100+

    resources on an ecommerce page Browsers limit the number of simultaneous connections to one server Wednesday, 7 August 13
  100. Domain Sharding To increase client side performance On average 100+

    resources on an ecommerce page Browsers limit the number of simultaneous connections to one server Hence limit the parallel download from one server Wednesday, 7 August 13
  101. Domain Sharding Use two or more CNAME aliases to serve

    the content from a CF distribution Wednesday, 7 August 13
  102. Domain Sharding Use two or more CNAME aliases to serve

    the content from a CF distribution Browser treat them as different servers Wednesday, 7 August 13
  103. Domain Sharding Use two or more CNAME aliases to serve

    the content from a CF distribution Browser treat them as different servers Sharding across 2 CNAME aliases will double the parallel download (Best 2-3) Wednesday, 7 August 13
  104. Domain Sharding Use two or more CNAME aliases to serve

    the content from a CF distribution Browser treat them as different servers Sharding across 2 CNAME aliases will double the parallel download (Best 2-3) More than 4 CNAME will degrade browser performance (high CPU and memory uses) Wednesday, 7 August 13
  105. Domain Sharding Use CF CNAME alias feature Use Route 53

    for CNAME Aliasing Wednesday, 7 August 13
  106. Domain Sharding Use CF CNAME alias feature Use Route 53

    for CNAME Aliasing Custom Wild Card SSL Certificate Wednesday, 7 August 13
  107. Domain Sharding Use CF CNAME alias feature Use Route 53

    for CNAME Aliasing Custom Wild Card SSL Certificate On application side: enable CF sharding logic (template compilation etc) Wednesday, 7 August 13
  108. Domain Sharding <span style="width:inherit;"> <a href="http://mysite.com/about"><img src="http://cf.mycloudfront.net/about.jpg" alt=""/></a> </span> <span

    style="width:inherit;"> <a href="http://mysite.com/blogs"><img src="http://cf.mycloudfront.net/blogs.jpg" alt=""/></a> </span> <span style="width:inherit;"> <a href="http://mysite.com/contact"><img src="http://cf.mycloudfront.net/cont.jpg" alt=""/></a> </span> <span style="width:inherit;"> <a href="http://mysite.com/about"><img src="http://cf1.mycloudfront.net/about.jpg" alt=""/></a> </span> <span style="width:inherit;"> <a href="http://mysite.com/blogs"><img src="http://cf2.mycloudfront.net/blogs.jpg" alt=""/></a> </span> <span style="width:inherit;"> <a href="http://mysite.com/contact"><img src="http://cf1.mycloudfront.net/cont.jpg" alt=""/></ a> </span> <span style="width:inherit;"> <a href="http://mysite.com/about"><img src="{{ CDN_DOMAINS }}/about.jpg" alt=""/></a> </span> <span style="width:inherit;"> <a href="http://mysite.com/blogs"><img src="{{ CDN_DOMAINS }}/blogs.jpg" alt=""/></a> </span> <span style="width:inherit;"> <a href="http://mysite.com/contact"><img src="{{ CDN_DOMAINS }}/cont.jpg" alt=""/></a> </span> <span style="width:inherit;"> <a href="http://mysite.com/about"><img src="http://mysite.com/about.jpg" alt=""/></a> </span> <span style="width:inherit;"> <a href="http://mysite.com/blogs"><img src="http://mysite.com/blogs.jpg" alt=""/></a> </span> <span style="width:inherit;"> <a href="http://mysite.com/contact"><img src="http://mysite.com/cont.jpg" alt=""/></a> </span> CDN with domain sharding CDN without domain sharding HTML Template Without CDN Compiled OR DOM Manipulation Compiled OR DOM Manipulation Wednesday, 7 August 13
  109. Domain Sharding Apply domain sharding only where it’s needed most

    Evenly distribute the resources amongst the shards Wednesday, 7 August 13
  110. Domain Sharding Apply domain sharding only where it’s needed most

    Evenly distribute the resources amongst the shards Consider performance overhead due to the DNS lookup and connection time Wednesday, 7 August 13
  111. Domain Sharding Apply domain sharding only where it’s needed most

    Evenly distribute the resources amongst the shards Consider performance overhead due to the DNS lookup and connection time Sharding may not be good for Mobile Browsers (CPU, Battery Life) Wednesday, 7 August 13
  112. Bucket Organisation Limited Cache Behavior per CF Distribution Plan your

    bucket organisation (object keys) Wednesday, 7 August 13
  113. Bucket Organisation Limited Cache Behavior per CF Distribution Plan your

    bucket organisation (object keys) Watch out for the upload paths Wednesday, 7 August 13
  114. Bucket Organisation Limited Cache Behavior per CF Distribution Plan your

    bucket organisation (object keys) Watch out for the upload paths /video/uploads/, /audio/uploads/, /images/uploads/ BAD Wednesday, 7 August 13
  115. Bucket Organisation Limited Cache Behavior per CF Distribution Plan your

    bucket organisation (object keys) Watch out for the upload paths /video/uploads/, /audio/uploads/, /images/uploads/ BAD /uploads/video/, /uploads/audio/, /uploads/image/ GOOD Wednesday, 7 August 13
  116. Bucket Organisation Limited Cache Behavior per CF Distribution Plan your

    bucket organisation (object keys) Watch out for the upload paths /video/uploads/, /audio/uploads/, /images/uploads/ BAD /uploads/video/, /uploads/audio/, /uploads/image/ GOOD Use wild card patterns (/uploads/*) Wednesday, 7 August 13
  117. Logging Enable logging, store access log file to S3 One

    log file per distribution Wednesday, 7 August 13
  118. Logging Enable logging, store access log file to S3 One

    log file per distribution Combine log files and analyze logs (EMR) Wednesday, 7 August 13
  119. Logging Enable logging, store access log file to S3 One

    log file per distribution Combine log files and analyze logs (EMR) W3C extended log file format Wednesday, 7 August 13
  120. Logging Enable logging, store access log file to S3 One

    log file per distribution Combine log files and analyze logs (EMR) W3C extended log file format Streaming log vs Download log Wednesday, 7 August 13
  121. Logging Enable logging, store access log file to S3 One

    log file per distribution Combine log files and analyze logs (EMR) W3C extended log file format Streaming log vs Download log Content Analytics: Popularity, Error etc Wednesday, 7 August 13
  122. Performance Testing Tradition Load Testing not useful Same DNS request,

    same set of IPs Backbone Testing (Ideal Word) Wednesday, 7 August 13
  123. Performance Testing Tradition Load Testing not useful Same DNS request,

    same set of IPs Backbone Testing (Ideal Word) CDN Server ˠ Backbone Wednesday, 7 August 13
  124. Performance Testing Tradition Load Testing not useful Same DNS request,

    same set of IPs Backbone Testing (Ideal Word) CDN Server ˠ Backbone Last Mile (Real World, User Experience) Wednesday, 7 August 13
  125. Performance Testing Tradition Load Testing not useful Same DNS request,

    same set of IPs Backbone Testing (Ideal Word) CDN Server ˠ Backbone Last Mile (Real World, User Experience) CDN Server ˠ Backbone ˠ Device Wednesday, 7 August 13
  126. Performance Testing Tradition Load Testing not useful Same DNS request,

    same set of IPs Backbone Testing (Ideal Word) CDN Server ˠ Backbone Last Mile (Real World, User Experience) CDN Server ˠ Backbone ˠ Device 3rd party service (Gomez), application monitor Wednesday, 7 August 13
  127. Performance Testing Tradition Load Testing not useful Same DNS request,

    same set of IPs Backbone Testing (Ideal Word) CDN Server ˠ Backbone Last Mile (Real World, User Experience) CDN Server ˠ Backbone ˠ Device 3rd party service (Gomez), application monitor Load Testing (Edge Location, Elastic IP Aware) Wednesday, 7 August 13
  128. Performance Testing Tradition Load Testing not useful Same DNS request,

    same set of IPs Backbone Testing (Ideal Word) CDN Server ˠ Backbone Last Mile (Real World, User Experience) CDN Server ˠ Backbone ˠ Device 3rd party service (Gomez), application monitor Load Testing (Edge Location, Elastic IP Aware) Clients request from different geolocations Wednesday, 7 August 13
  129. Performance Testing Tradition Load Testing not useful Same DNS request,

    same set of IPs Backbone Testing (Ideal Word) CDN Server ˠ Backbone Last Mile (Real World, User Experience) CDN Server ˠ Backbone ˠ Device 3rd party service (Gomez), application monitor Load Testing (Edge Location, Elastic IP Aware) Clients request from different geolocations Independent DNS request, different set of IPs Wednesday, 7 August 13
  130. Performance Testing Tradition Load Testing not useful Same DNS request,

    same set of IPs Backbone Testing (Ideal Word) CDN Server ˠ Backbone Last Mile (Real World, User Experience) CDN Server ˠ Backbone ˠ Device 3rd party service (Gomez), application monitor Load Testing (Edge Location, Elastic IP Aware) Clients request from different geolocations Independent DNS request, different set of IPs Distribute load across set of IPs Wednesday, 7 August 13